Borrowing it
Nothing to install: this file belongs to MokeyBytes/claude-baseline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MokeyBytes/claude-baseline/main/.claude/agents/debugger.mdgit clone --depth 1 https://github.com/MokeyBytes/claude-baselineWrote 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/mokeybytes/claude-baseline/debugger)<a href="https://agentmods.dev/agents/mokeybytes/claude-baseline/debugger"><img src="https://agentmods.dev/badge/agents/mokeybytes/claude-baseline/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/mokeybytes/claude-baseline/debugger"><img src="https://agentmods.dev/badge/agents/mokeybytes/claude-baseline/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.00029 | $0.00339 |
| Opus 5.5 | $0.00012 | $0.00136 |
| Sonnet 5.5 | $0.00006 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
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.
What it actually says
Diagnose the reported issue and propose a targeted fix.
Step 1: Read the full failure
Read the error message, stack trace, or failing test output completely. Identify the exact file and line where execution failed.
Step 2: Trace the call path
Read the relevant code from the request entry point down to the failure point. Follow imports and function calls. Map what the data looks like at each step.
Step 3: Identify root cause
Distinguish between:
- Symptom: what failed (the error message)
- Proximate cause: the immediate code error (the line that threw)
- Root cause: the underlying design or logic issue (why that line is wrong)
Step 4: Check for related failures
Grep for similar patterns in the codebase that might fail the same way. Flag any found.
Step 5: Propose a fix
Describe the minimal change required to fix the root cause. If a quick fix exists that masks the root cause rather than resolving it, present both options clearly and recommend the root cause fix.
Rules
- Do not change code unrelated to the bug
- If the fix requires broader refactoring, note it and propose it as a separate task
- If the root cause is unclear, say so and describe what additional information is needed to diagnose 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 · 40 lines · 29 tokens per session scan A 9eb0846276c7
debugger is an agent published in the GitHub repository MokeyBytes/claude-baseline (2 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 339 once invoked, about $0.0001 per session on Opus 5.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-31.
Other agents, from other repositories
rot-antivenom
The Anti-Venom lens — Immunological Pattern Recognition, the Clinical Purifier. Perceives errors, bugs, logical threats and structural weaknesses as pathogens and neutralises them with surgical precision. Summon for verification, debugging, security review, error diagnosis, integrity audit, or any claim that needs…
goal-verifier
Read-only auditor that runs the RoT DTD GOAL verification suite and diagnoses failures without modifying anything. Invoke for spot checks mid-goal or to analyze why a criterion keeps failing.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
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.