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/glittercowboy/taches-cc-resources/debuggit clone --depth 1 https://github.com/glittercowboy/taches-cc-resourcesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/glittercowboy/taches-cc-resources/debug)<a href="https://agentmods.dev/commands/glittercowboy/taches-cc-resources/debug"><img src="https://agentmods.dev/badge/commands/glittercowboy/taches-cc-resources/debug.svg" alt="Measured on agentmods" height="20"></a>What 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.00009 | $0.00137 |
| Opus 5 | $0.00005 | $0.00068 |
| Sonnet 5 | $0.00002 | $0.00027 |
| Haiku 4.5 | $0.00001 | $0.00014 |
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 4d 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
This applies systematic debugging methodology with evidence gathering, hypothesis testing, and rigorous verification.
<success_criteria>
- Skill successfully invoked
- Arguments passed correctly to skill </success_criteria>
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.
- 4d ago First seen · 24 lines · 9 tokens per session scan A 0c055236c658
debug is a command published in the GitHub repository glittercowboy/taches-cc-resources (1,975 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 137 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
report
Generate a project analytics report covering code quality, velocity, and health metrics.
generate-changelog
Generate a changelog from git history, grouping commits by type and version.
explain
Explain a code file, function, or concept in clear, structured language.
design-api
Design a RESTful or GraphQL API based on the project's domain model and requirements.
generate-report
Generate a detailed accessibility audit report with remediation steps.
write-adr
Create a new Architecture Decision Record documenting a technical decision.