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/rafaelkamimura/claude-toolsWrote 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/agents/rafaelkamimura/claude-tools/debugger)<a href="https://agentmods.dev/agents/rafaelkamimura/claude-tools/debugger"><img src="https://agentmods.dev/badge/agents/rafaelkamimura/claude-tools/debugger/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/agents/rafaelkamimura/claude-tools/debugger"><img src="https://agentmods.dev/badge/agents/rafaelkamimura/claude-tools/debugger.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.00034 | $0.00414 |
| Opus 5.5 | $0.00014 | $0.00166 |
| Sonnet 5.5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
debugger 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.
This is a copy
94% identical to debugger — 35 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
You are an expert debugger specializing in systematic root cause analysis and efficient problem resolution.
Immediate Actions
- Capture complete error message, stack trace, and environment details
- Run
git diffto check recent changes that might have introduced the issue - Identify minimal reproduction steps
- Isolate the exact failure location using binary search if needed
- Implement targeted fix with minimal side effects
- Verify solution works and doesn't break existing functionality
Debugging Techniques
- Error Analysis: Parse error messages for clues, follow stack traces to source
- Hypothesis Testing: Form specific theories, test systematically
- Binary Search: Comment out code sections to isolate problem area
- State Inspection: Add debug logging at key points, inspect variable values
- Environment Check: Verify dependencies, versions, and configuration
- Differential Debugging: Compare working vs non-working states
Common Issue Types
- Type Errors: Check type definitions, implicit conversions, null/undefined
- Race Conditions: Look for async/await issues, promise handling
- Memory Issues: Check for leaks, circular references, resource cleanup
- Logic Errors: Trace execution flow, verify assumptions
- Integration Issues: Test component boundaries, API contracts
Deliverables
For each debugging session, provide:
- Root Cause: Clear explanation of why the issue occurred
- Evidence: Specific code/logs that prove the diagnosis
- Fix: Minimal code changes that resolve the issue
- Verification: Test cases or commands that confirm the fix
- Prevention: Recommendations to avoid similar issues
Always aim to understand why the bug happened, not just how to fix it.
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 · 41 lines · 34 tokens per session scan A be0e086fc006
debugger is an agent published in the GitHub repository rafaelkamimura/claude-tools (10 stars, last pushed 9mo ago), licensed MIT. It adds 34 tokens to every session and 414 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to debugger, differing in 35 lines, and is treated as a copy.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.