Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/cpj-dev/dsh-plugin-cc/rungit clone --depth 1 https://github.com/cpj-dev/dsh-plugin-ccWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00018 | $0.00518 |
| Opus 5 | $0.00009 | $0.00259 |
| Sonnet 5 | $0.00004 | $0.00104 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
run scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Run a task on DeepSeek Harness:
node "${CLAUDE_PLUGIN_ROOT}/scripts/dsh-bridge.mjs" run "$ARGUMENTS"
Flags (explain to the user when relevant):
- Default: one-shot headless run, read-only sandbox. Crash-isolated, not resumable.
--write: allow workspace file edits (workspace-write sandbox).--session: run through the shared broker and record a resumable dsh session id.--resume(or--resume-last): continue the most recent recorded dsh session; new text becomes the follow-up prompt, empty means "continue". The resume is validated against the live broker runtime — if the broker was stopped or restarted since, the command errors and asks for a fresh--sessioninstead of silently starting over (relay that to the user).--model <name>/--effort low|high|max: per-run model selection (ignored on--resume; the broker keeps its startup model). Defaults:deepseek-v4-proat effortmax.lowis in the official schema;mediumis not. A vision id such asdeepseek-v4-flash-vision-expdoes not attach Claude chat images — this plugin sends text only.--mode minimal|standard|anchored-standard: agent mode. Defaultstandard(full dsh toolset from request #1, no overlay).minimallocks bash + str_replace_editor for the whole run.anchored-standardshows that pair until this session records a tool call or assistant reply, then restores the full catalog. Ignored on--resume; a live broker keeps its startup mode, and a--sessionrun whose mode differs from the live broker errors with a/dsh:stop --brokerhint — relay that to the user./dsh:setup --mode <m>persists a machine default.--background: queue the run, return a run id, check with/dsh:runs.
Before suggesting --resume, you may probe availability with:
node "${CLAUDE_PLUGIN_ROOT}/scripts/dsh-bridge.mjs" run-resume-candidate
Present the run output verbatim, including the footer line with the run id and session id.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 28 lines · 18 tokens per session scan A 39f2f0f132d9
run is a command published in the GitHub repository cpj-dev/dsh-plugin-cc (106 stars, last pushed 5d ago), licensed MIT. It adds 18 tokens to every session and 518 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
review
Run an adversarial review. Raw arguments: $ARGUMENTS.
ship
Prepare a release checklist.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.