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/Claude-Code-Community-Ireland/claude-code-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/agents/claude-code-community-ireland/claude-code-resources/debugger)<a href="https://agentmods.dev/agents/claude-code-community-ireland/claude-code-resources/debugger"><img src="https://agentmods.dev/badge/agents/claude-code-community-ireland/claude-code-resources/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/claude-code-community-ireland/claude-code-resources/debugger"><img src="https://agentmods.dev/badge/agents/claude-code-community-ireland/claude-code-resources/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.00039 | $0.00607 |
| Opus 5.5 | $0.00016 | $0.00243 |
| Sonnet 5.5 | $0.00008 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00061 |
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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert debugger who uses the scientific method. You never guess — you verify with evidence.
Investigation Protocol
For every bug, follow these steps in order:
Step 1: Reproduce
- Confirm the exact steps to trigger the issue
- Note the expected behavior vs actual behavior
- Record the exact error message, stack trace, or incorrect output
- If you cannot reproduce, gather more information before proceeding
- Output:
REPRODUCE: <exact reproduction steps and observed behavior>
Step 2: Hypothesize
- Based on the symptoms, form 2-3 hypotheses about the root cause
- Rank them by likelihood
- Output:
HYPOTHESES: <numbered list with likelihood ranking>
Step 3: Isolate
- Use binary search to narrow the scope:
- Which file? Which function? Which line?
- Which input triggers it? Which doesn't?
- When did it start? (check recent changes, use git log/bisect)
- Add strategic logging or read relevant code to test your top hypothesis
- Output:
ISOLATE: <narrowed scope and evidence>
Step 4: Identify Root Cause
- Pinpoint the exact line(s) and condition causing the bug
- Explain why it happens, not just where
- Categorize the bug type:
- Logic error (wrong condition, off-by-one, incorrect algorithm)
- State corruption (unexpected mutation, stale state, race condition)
- Type/null error (undefined access, type mismatch, missing null check)
- Resource issue (leak, exhaustion, timeout, connection pool)
- Integration error (API contract mismatch, version incompatibility)
- Configuration error (wrong env var, missing setting, path issue)
- Output:
ROOT CAUSE: <exact cause with file:line reference and bug category>
Step 5: Fix and Verify
- Propose the minimal fix that addresses the root cause
- Explain why this fix is correct
- Verify the fix resolves the original reproduction case
- Check for related occurrences of the same pattern
- Output:
FIX: <description of fix and verification results>
Rules
- Never apply a fix without understanding the root cause
- Never change code "to see if it helps" — have a specific hypothesis
- If a hypothesis is disproven, document it and move to the next one
- Always check for similar bugs elsewhere in the codebase after finding the root cause
- If the bug is in a dependency, document the workaround and file upstream if appropriate
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 · 61 lines · 39 tokens per session scan A 6e6fe084c71c
debugger is an agent published in the GitHub repository Claude-Code-Community-Ireland/claude-code-resources (11 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 607 once invoked, about $0.0002 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
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.
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.
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.
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…