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/dinhnguyenngoc/spec-driven-claude-code/debuggit clone --depth 1 https://github.com/dinhnguyenngoc/spec-driven-claude-codeWhat 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.00015 | $0.03186 |
| Opus 5 | $0.00008 | $0.01593 |
| Sonnet 5 | $0.00003 | $0.00637 |
| Haiku 4.5 | $0.00002 | $0.00319 |
Grade A, and why
debug 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.
How it starts
The opening of the file, as written. The whole thing — 395 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/debug — Debugging & Error Recovery
"Fix root causes, not symptoms."
Purpose
Systematically diagnose and fix errors. Stop feature work, preserve evidence, find root cause, add guards, then resume.
Workspace Mode: if the session root declares
Mode: workspace→ resolve the target repo perCLAUDE.md§Workspace Mode before anything else; every path, probe, and gate below is relative to the target repo, and the workspace disk-check applies at the gate.
Stack Profile note: the
dotnetcommands, triage trees, error catalog, and §Debugging Tools below use the default profile. Core = Node.js → map accordingly (npm test/npx vitest --reporter=verbose,node --inspect, Prismalog: ['query']instead of EF Core logging) — the .NET error catalog is default-stack illustration only. Core = PHP →php artisan test/vendor/bin/pest --filter <name>, Xdebug for step-debugging,DB::enableQueryLog()/ Laravel Telescope instead of EF Core query logging (rules/overrides/lang-php.mdidioms apply).
Agent
Invoke based on the layer where the error occurs:
| Error Layer | Agent |
|---|---|
| API, service, DB, background job | 🔧 Backend Developer |
| Component, page, routing, UI | 🖥️ Frontend Developer |
| Test failure (flaky, intermittent) | 🧪 Test Engineer |
| Security-related error | 🔒 Security Auditor |
Sub-agent prompt MUST include: "Output language: <declared language — resolve from Project Profile → Output Language> for prose/artifacts, English for code and technical identifiers (see
.claude/CLAUDE.md→ Output Language)."
Sub-agent prompt MUST also include: "Ambiguity policy: implementation details → decide per rules, never ask; non-blocking behavior/contract gaps → implement the most conservative interpretation and add an Assumptions-log entry (
A-xx— when a/buildphase is running it joins that phase's log, dispositioned at Gate 5; with no running phase — standalone debug, or a/test//reviewcontext — the user dispositions it before this debug closes, same mechanism as/fix-issue); blocking or expensive-if-wrong gaps → stop and return early with the question (seerules/principles-and-practices.md§2.5). Return everyA-xxentry (or 'Assumptions: none') in your completion report — the orchestrator routes it: into the running/buildphase's log (Gate 5), or to the user's immediate disposition when no phase is running."
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 · 395 lines · 15 tokens per session scan A 2fbd768286ee
debug is a command published in the GitHub repository dinhnguyenngoc/spec-driven-claude-code (20 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 3,186 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
brooks-audit
Run a Brooks-Lint architecture audit.
autospec.plan
Generate YAML implementation plan from feature specification.
kiro-validate-design
Command "kiro-validate-design" from gotalab/cc-sdd, covering technical design validation, core task, execution steps, important constraints and tool guidance.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
sdd-setup
Onboarding wizard — DocLanguage, Memory Bank, architecture snapshot, working agreements (quality gate, TDD working mode).
fix
⚡⚡ Analyze and fix small issues [AUTO DETECT COMPLEXITY].