Verification toolkit for DSH agents: evidence-based claim checking against workspace files with line citations, config validation (JSON/YAML), and read-only URL/npm/GitHub submission-readiness probes.
Install
# from npm (prebuilt)
dsh plugin --profile web add dsh-plugin-verify
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:863683348/dsh-plugin-verify
Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).
README
Verification toolkit for DeepSeek Harness agents — evidence-based claim checking, config validation, and read-only network probes (URL / npm / GitHub).
Compatibility
Tool schemas are validated against the @deepseek-ai/dsh-tools value-schema DSL at plugin load (checked against dsh-tools 0.1.0-rc.6 and 0.1.1-rc.2). Earlier releases used JSON-Schema required at the root of output.schema and closed nested objects without declared properties, which made the host abort the whole profile boot with unsupported JSON schema: schema.required is not supported by the value schema DSL and could reject the tool's own results. Current releases fix both; if an affected version left your DSH unable to start, remove the plugin from the profile (or upgrade) — no data is lost.
Tools
| Tool | Mode | What it does |
|---|---|---|
verify |
claim |
Verify a statement against workspace files: keyword extraction, per-keyword hits with line-level citations, verdict verified / partial / unsupported |
config |
Validate a config file — JSON strict parse or YAML structural smoke check | |
url |
HTTP(S) availability: status, redirect target, latency | |
npm |
Registry check: exists, latest version, dsh.bundle manifest, publish time |
|
repo |
GitHub submission-readiness: exists, age, dsh-plugin topic, approximate commit count |
|
batch |
Run many checks at once (claims / configs / urls / packages / repos) with bounded concurrency, a summary table and a per-result confidence grade |
Usage
verify claim "the plugin pins zod in dependencies" # evidence search in workspace
verify claim "this repo has 12 commits" scope ./some-dir
verify config ./cordis.patch.yml
verify url https://example.com
verify npm dsh-plugin-focus
verify repo 863683348/dsh-plugin-gate
verify batch claims:["the plugin pins zod"] urls:["https://example.com"] packages:["dsh-plugin-focus"]
Notes
- Read-only: never writes files, never executes scanned content.
- Claim verification is a heuristic (keyword evidence), not proof — an
unsupportedverdict means "no evidence found", treat it as unconfirmed. - YAML check is a structural smoke check (balanced quotes/brackets, indentation), not a full YAML parser.
Development
node --check lib/*.js
node test/verify.test.mjs
License
MIT
Roadmap
See ROADMAP.md — next five versions (v1.1.0 – v1.5.0): batch & confidence, reports & regression, strict validation, probe hardening, submission-readiness expansion.
Links
More in this category
yjh051108/dsh-routing-suite★ 6990
One repository, three parts: a runtime injector for DSH plugin packages (inject, hot-reload, unload, promote a dev staging tool to the front, route self-heal, plus a settings-page plugin manager that lists, unloads and drags folders in to internalize), a task-aware reasoning-mode router agent preset (router-standard / router-spec / router-react), and a graded two-level task protocol whose six tools (commit_star, lock_stage, revise_do, edit_plan, mark_task, redteam_verdict) pin task state to disk. The injector implementation ships in-tree, so the install carries its own behaviour rather than a dependency list.
strukto-ai/mirage#dsh★ 3670
Swaps the filesystem and bash providers for a mirage virtual workspace: file tools and shell commands run over mounted resources (RAM, S3, Redis, Slack, Gmail, Notion, Postgres) instead of the host disk, with per-mount read/write/exec modes, per-command sandbox routing (monty, pyodide, quickjs in process; docker, e2b, daytona remote), and installed CLIs (git, gh, slack, linear, ntn, gws, or one you register) as head words in the virtual terminal.
hust-open-atom-club/oh-dsh★ 325
Community distribution: TUI, desktop, and Web UI as one bundle with layered installation.
weijiafu14/pi2dsh★ 210
Pi Host ABI compatibility engine: after one install, unmodified Pi extensions from npm mount as native DSH plugins with `dsh plugin add <pi-package>`. Verified end to end on stock DSH with pi-mcp-adapter (full MCP manager: OAuth, resources, prompts, MCP Apps, elicitation, sampling), @tintinweb/pi-subagents, pi-code, pi-hermes-memory and pi-background-tasks; `pi2dsh inspect` reports a package's compatibility before installing.
lire1131/dsh-undo-savepoint★ 168
Undo/redo & rollback system for DSH: every config change is auto-snapshotted; undo/redo/restore to any version from the WebUI or the offline CLI/GUI tools (works even when DSH fails to boot).
Fishquito7/dsh-skill-mcp-panel★ 161
Manages DSH skills and MCP servers from the web settings: skill cards with hot enable/disable, workspace scopes, groups, batch migration and drag-and-drop import, plus stdio/HTTP MCP CRUD with connection tests, secret redaction and the unified dsh-panel CLI.
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.