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/checkgit 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.00019 | $0.00159 |
| Opus 5 | $0.00010 | $0.00079 |
| Sonnet 5 | $0.00004 | $0.00032 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
check 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 yesterday.
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 the readiness probe and show the user the result verbatim:
node "${CLAUDE_PLUGIN_ROOT}/scripts/dsh-bridge.mjs" check
If the report says "not ready", relay the listed next steps. Do not attempt to install anything yourself unless the user asks; when dsh is missing entirely, the fix is a single command — /dsh:setup installs the pinned @deepseek-ai/dsh from npm and creates the multi-turn cc profile. Users with their own built checkout can pass /dsh:setup --harness <path> instead.
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.
- yesterday First seen · 13 lines · 19 tokens per session scan A 2005dec7b46f
check is a command published in the GitHub repository cpj-dev/dsh-plugin-cc (106 stars, last pushed 5d ago), licensed MIT. It adds 19 tokens to every session and 159 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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.