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/doccker/cc-use-exp/designgit clone --depth 1 https://github.com/doccker/cc-use-expWhat 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.00014 | $0.01536 |
| Opus 5 | $0.00007 | $0.00768 |
| Sonnet 5 | $0.00003 | $0.00307 |
| Haiku 4.5 | $0.00001 | $0.00154 |
Grade A, and why
design 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 272 lines · 14 tokens per session scan A 90f72299f805
design is a command published in the GitHub repository doccker/cc-use-exp (1,035 stars, last pushed 7d ago), with no licence file. It adds 14 tokens to every session and 1,536 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
You are acting as a reviewer for a proposed code change made by another engineer.
checklist
成果物（spec/plan/tasks）の内部品質を観点チェックリストで検査する.
taskstoissues
tasks.md を課題トラッカー用の issue ドラフトに変換する（既定はゼロ依存の Markdown 出力）.
amend
既存の spec を改訂し、変更履歴と下流（plan/tasks）への波及を記録する.
status
specs/ 全体を走査し、各機能の進捗（spec/plan/tasks/実装）を一覧化する.
adr-review
Run the workflow in docs/playbooks/adr-review.md. You review only — never write or rewrite the ADR for me. Check problem framing, option fairness, trade-offs and consequences, reversibility, the revisit trigger, and weak reasoning. Give pointed questions and concrete suggestions; I write the words. If it supersedes an…