DeepSeek Harness plugin

dsh-verify-gate

Engineering verify gate for DeepSeek Harness: configured commands are authority; dirty receipts block conclude.

Jump to install

Source facts

Repository
blueWhalei/dsh-verify-gate
Latest update
Aug 14, 2026
Category
Security & Permissions
GitHub stars
0
Format
plugin
Catalog evidence
Upstream dsh.bundle evidence
Evidence path
package.json#dsh.bundle
Checked against
0.1.0-rc.8
Upstream check date
2026-08-20

This evidence comes from the upstream catalog. This site has not installed, run, or security-reviewed the plugin.

Install

Start with a prompt that asks an agent to review the GitHub repository and source. Switch to the command if you want to install it yourself.

Copy this prompt into DSH, Codex, or another agent and ask it to review the GitHub repository and source first.

Do not install or run any commands yet. Read this plugin's GitHub repository, README, and relevant source code. Then answer the questions below clearly and directly so I can decide whether it fits my needs:

1. What is this plugin, and what problem does it solve?
2. Who is it for, and what are its typical use cases?
3. How is it used after installation? Include one minimal example.
4. What known limitations or privacy, security, compatibility, or maintenance risks does it have?
5. Give a clear recommendation: recommend, conditionally recommend, or do not recommend, with reasons.

Distinguish statements documented by the repository, inferences from source code, and unknowns. If evidence is insufficient, say so explicitly. Do not guess or simply repeat the README.

GitHub: https://github.com/blueWhalei/dsh-verify-gate
Plugin: dsh-verify-gate
Author: blueWhalei

Check the source files

Read the README and other files from this plugin directory before installing.

File explorer4 files
README.mdSource · read only
README language

dsh-verify-gate

English | 中文

An open-source DeepSeek Harness plugin that requires the agent to run the workspace’s verification commands before it can conclude that work is done.

Pass/fail is decided only by process exit codes. A successful run writes an auditable receipt. After that, any successful mutating tool (for example edit, write, or bash) invalidates the receipt, so verification must pass again before conclude.

Install

Local path:

dsh plugin --profile web add /absolute/path/to/verify-gate

Or from GitHub (the repo includes the built lib/ entry points):

dsh plugin --profile web add github:blueWhalei/dsh-verify-gate

Restart Web, open the target workspace, then:

1. Run /verify run, or have the model call verify_run 2. Call verify_conclude only after every command exits 0

How commands are chosen

Resolution order:

1. Non-empty config.commands always wins 2. Otherwise auto-detect (on by default) requires exactly one common workspace marker: - package.json with scripts.test → pick the package manager from the lockfile / packageManager, then run <pm> test - go.modgo test ./... - Cargo.tomlcargo test 3. If nothing matches, or more than one ecosystem matches → fail with an error that asks you to set commands, instead of guessing

For Python, Java, and other stacks with many local conventions, set commands explicitly.

Custom config

Change config only when the default is wrong. Put this in the profile’s cordis.patch.yml (it replaces that plugin’s entire config):

- id: dsh-verify-gate
  name: dsh-verify-gate
  config:
    commands:
      - id: test
        run: pytest -q
    autoDetect: true
    sandboxMode: danger-full-access

sandboxMode defaults to danger-full-access so package managers can use a global store. If you tighten the sandbox, confirm the verify commands still run for real.

Everyday entry points

GoalEntry
Run verificationverify_run or /verify run
Inspect gate statusverify_status or /verify
Concludeverify_conclude (needs a green, non-dirty, non-expired receipt)

Receipts are stored under <workspace>/.dsh/verify-receipts/. Most application repos should ignore that directory.

License

MIT