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.
git clone --depth 1 https://github.com/Justdvp/claude-code-templatesWrote 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/justdvp/claude-code-templates/debug)<a href="https://agentmods.dev/commands/justdvp/claude-code-templates/debug"><img src="https://agentmods.dev/badge/commands/justdvp/claude-code-templates/debug/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/justdvp/claude-code-templates/debug"><img src="https://agentmods.dev/badge/commands/justdvp/claude-code-templates/debug.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00318 |
| Opus 5.5 | $0.00000 | $0.00127 |
| Sonnet 5.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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- debug — 100% identical, 0 lines differ
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.
- 1mo ago First seen · 52 lines · 0 tokens per session scan A 1ebf63ad8347
debug is a command published in the GitHub repository Justdvp/claude-code-templates (7 stars, last pushed 5d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
fix
A code-repair command that detects and fixes errors reported by language servers, linters, or type checkers. These tools find code problems such as invalid syntax, style issues, and mismatched data types.
clean
A command for finding code that is no longer used and removing it after checking that tests still pass.
debug-pod
Debug a failing or unhealthy Kubernetes pod by analyzing events, logs, and configuration.
map
Generate a dependency map showing how modules and files relate to each other in the codebase.
local
Command "local" from getsentry/toolkit, covering examples, start the server and tail events (default), run your app with the local server auto-enabled, use a custom port and only show errors and logs (filter out transactions).
feedback
Modern User Feedback is stored as Feedback issues. The command always limits issue searches to issue.category:feedback; it does not use the legacy User Reports API.