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/mkhrdev/cc-spec-driven/dd-spec-devgit clone --depth 1 https://github.com/mkhrdev/cc-spec-drivenWhat 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.00008 | $0.00355 |
| Opus 5 | $0.00004 | $0.00178 |
| Sonnet 5 | $0.00002 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
dd-spec-dev 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 · 61 lines · 8 tokens per session scan A 8207745438ad
dd-spec-dev is a command published in the GitHub repository mkhrdev/cc-spec-driven (29 stars, last pushed 7mo ago), with no licence file. It adds 8 tokens to every session and 355 once invoked, about $0.0000 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
run-plan
Execute a PLAN.md file directly without loading planning skill context.
heal-skill
Heal skill documentation by applying corrections discovered during execution with approval workflow.
whats-next
Analyze the current conversation and create a handoff document for continuing this work in a fresh context.
add-to-todos
Add todo item to TO-DOS.md with context from conversation.
check-todos
List outstanding todos and select one to work on.
run-prompt
Delegate one or more prompts to fresh sub-task contexts with parallel or sequential execution.