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/valsecchi75/project-scaffolder/debuggit clone --depth 1 https://github.com/valsecchi75/project-scaffolderWhat 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.00033 | $0.00397 |
| Opus 5 | $0.00016 | $0.00198 |
| Sonnet 5 | $0.00007 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00040 |
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.
What it actually says
/debug
Structured debugging (Karpathy debug principle). Do NOT guess — reproduce and isolate first.
Usage
/debug <symptom description>
Examples
/debug App crashes when adding a subscription with empty name
/debug DateFormat throws on Android 11 with IT locale
/debug Isar query returns stale data after save
Phases
- Reproduce — write exact steps that trigger the bug. Confirm reproducibility.
- Isolate — binary-search the cause. Identify the minimum failing case.
- Hypothesize — list 2-3 hypotheses, ranked by likelihood.
- Diagnose — verify the top hypothesis with evidence (log, stack trace, diff).
- Fix — the minimum change that resolves the diagnosed cause.
- Verify — re-run repro steps, confirm fixed, add a regression test where appropriate.
- Document — atomic operations:
- Append entry to
wiki/debugging/known-errors.md(IDKE-NNN) - Append entry to
guardrails/errors-to-avoid.md(IDERR-NNN, cross-referenced to KE-NNN) - Call Synapse to propagate the lesson to connected skills
- Append entry to
Rules
- NEVER skip Reproduce. If you can't reproduce, the bug is not understood.
- Prefer one small fix over a wide refactor.
- If root cause is shared infrastructure → flag Synapse for multi-skill propagation.
- If stuck after 3 hypotheses: STOP, ask the user for more context or escalate.
- Every
/debugsession ends with either a fix + documentation, or an explicit[INVESTIGATING]entry.
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 · 44 lines · 33 tokens per session scan A 178b509f858a
debug is a command published in the GitHub repository valsecchi75/project-scaffolder (9 stars, last pushed 29d ago), licensed MIT. It adds 33 tokens to every session and 397 once invoked, about $0.0002 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-31.
Other commands, from other repositories
learn
Force claude-smart to extract learnings from this session now.
component
Scaffold a new React component grounded in the paper-mono primitives. Requires explicit kind or a nearest-existing-component match. No empty divs, no speculative scaffolding.
memory-store
Store an insight, decision, or pattern to memory.
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
no-vibe
Enter no-vibe mode in OpenCode (tutor mode, no direct project file writes).
teach-me-testing
Teach testing progressively through structured sessions. Use when user says ""lets learn testing"" or ""I want to study test practices"".