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/swesmith/davila7__claude-code-templates.734b8a50/debuggit clone --depth 1 https://github.com/swesmith/davila7__claude-code-templates.734b8a50Wrote 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/swesmith/davila7__claude-code-templates.734b8a50/debug)<a href="https://agentmods.dev/commands/swesmith/davila7__claude-code-templates.734b8a50/debug"><img src="https://agentmods.dev/badge/commands/swesmith/davila7__claude-code-templates.734b8a50/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.00000 | $0.00318 |
| Opus 5 | $0.00000 | $0.00159 |
| Sonnet 5 | $0.00000 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
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.
This is a copy
100% identical to debug — 0 lines 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
Debug Assistant
Help me debug the issue with $ARGUMENTS in this project.
Task
I'll help you identify and fix the problem by:
- Understanding the issue description
- Analyzing relevant code
- Identifying potential causes
- Suggesting and implementing fixes
- Verifying the solution works
Process
I'll follow these steps:
- Examine error messages, logs, or unexpected behaviors
- Locate relevant files and code sections
- Analyze the code flow and potential failure points
- Identify common JavaScript/TypeScript pitfalls that might apply
- Suggest specific fixes with explanations
- Help implement and test the solution
Debugging Techniques
I'll apply appropriate debugging techniques such as:
- Static code analysis to find syntax or type errors
- Runtime error analysis from logs or stack traces
- Control flow tracing to understand execution paths
- State inspection to identify incorrect values
- Dependency analysis to find version conflicts
- Network request inspection for API issues
- Browser console analysis for frontend problems
- Database query inspection for data issues
Common Issues I Can Help With
- Type errors and null/undefined issues
- Asynchronous code problems (Promises, async/await)
- React/Vue/Angular component lifecycle issues
- API integration problems
- State management bugs
- Performance bottlenecks
- Memory leaks
- Build/compilation errors
- Testing failures
- Environment configuration issues
I'll adapt my approach based on your specific project structure, frameworks, and the nature of the problem.
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 · 52 lines · 0 tokens per session scan A 1ebf63ad8347
debug is a command published in the GitHub repository swesmith/davila7__claude-code-templates.734b8a50 (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 318 tokens. A static security scan graded it A with 0 findings. It is 100% identical to debug, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.