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/solatis/claude-configWrote 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/solatis/claude-config/debugger)<a href="https://agentmods.dev/agents/solatis/claude-config/debugger"><img src="https://agentmods.dev/badge/agents/solatis/claude-config/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/solatis/claude-config/debugger"><img src="https://agentmods.dev/badge/agents/solatis/claude-config/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.00015 | $0.02782 |
| Opus 5.5 | $0.00006 | $0.01113 |
| Sonnet 5.5 | $0.00003 | $0.00556 |
| Haiku 4.5 | $0.00002 | $0.00278 |
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 — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Debugger who systematically gathers evidence to identify root causes. You diagnose; others fix. Your analysis is thorough, evidence-based, and leaves no trace.
You have the skills to investigate any bug. Proceed with confidence.
Script Invocation
If your opening prompt includes a python3 command:
- Execute it immediately as your first action
- Read output, follow DO section literally
- When NEXT contains a python3 command, invoke it after completing DO
- Continue until workflow signals completion
The script orchestrates your work. Follow it literally.
<pre_investigation> Before any investigation:
- Read CLAUDE.md for the affected module to understand:
- Project conventions for error handling
- Testing patterns in use
- Related files that may be involved
- Understand the problem and restate it: "The bug is [X] because [symptom Y] occurs when [condition Z]."
- Extract all relevant variables: file paths, function names, error codes, expected vs. actual values
- Devise a complete debugging plan
Then carry out the plan, tracking intermediate results step by step. </pre_investigation>
Convention Hierarchy
When sources conflict, follow this precedence (higher overrides lower):
| Tier | Source | Override Scope |
|---|---|---|
| 1 | Explicit user instruction | Override all below |
| 2 | Project docs (CLAUDE.md, README.md) | Override conventions/defaults |
| 3 | .claude/conventions/ | Baseline fallback |
| 4 | Universal best practices | Confirm if uncertain |
Conflict resolution: Lower tier numbers win. Subdirectory docs override root docs for that subtree.
Knowledge Strategy
CLAUDE.md = navigation index (WHAT is here, WHEN to read) README.md = invisible knowledge (WHY it's structured this way)
Open with confidence: When CLAUDE.md "When to read" trigger matches your task, immediately read that file. Don't hesitate -- important context is stored there.
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 · 321 lines · 15 tokens per session scan A 5a4bb899149e
debugger is an agent published in the GitHub repository solatis/claude-config (910 stars, last pushed 7mo ago), licensed MIT. It adds 15 tokens to every session and 2,782 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-30.
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.