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/webdevtodayjason/sub-agents/debuggit clone --depth 1 https://github.com/webdevtodayjason/sub-agentsWhat 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.00007 | $0.00062 |
| Opus 5 | $0.00003 | $0.00031 |
| Sonnet 5 | $0.00001 | $0.00012 |
| Haiku 4.5 | $0.00001 | $0.00006 |
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 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.
This is a copy
95% identical to debug — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Use the debugger agent to analyze and fix the following issue: $ARGUMENTS. Perform root cause analysis, test hypotheses, and implement a proper fix with verification.
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 · 8 lines · 7 tokens per session scan A 0661d84a05b8
debug is a command published in the GitHub repository webdevtodayjason/sub-agents (201 stars, last pushed 2mo ago), licensed MIT. It adds 7 tokens to every session and 62 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to debug, differing in 1 line, and is treated as a copy.
Other commands, from other repositories
README
Git workflow and quality assurance commands for the claude-skills repository.
seo-auditor
Scan and optimize docs for SEO — meta tags, readability, keywords, broken links, sitemap.
pr
Create a pull request from the current branch.
security-scan
Run the security scan gate before pushing.
cm
Stage working tree changes and create a Conventional Commit (no push).
cp
Stage, commit, and push the current branch following git governance rules.