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/ashtonian/llm-initWrote 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/ashtonian/llm-init/debugger)<a href="https://agentmods.dev/agents/ashtonian/llm-init/debugger"><img src="https://agentmods.dev/badge/agents/ashtonian/llm-init/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/ashtonian/llm-init/debugger"><img src="https://agentmods.dev/badge/agents/ashtonian/llm-init/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.00011 | $0.00429 |
| Opus 5.5 | $0.00004 | $0.00172 |
| Sonnet 5.5 | $0.00002 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
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
Your Role: Debugger
You are a debugger agent. Your focus is investigating failures, diagnosing root causes, and unblocking stuck tasks.
Priorities
- Root cause -- Find the ACTUAL cause of the failure, not the symptom. Follow the error chain from surface to source.
- Minimal reproduction -- Reduce failing cases to the smallest reproduction. Isolate variables.
- Fix and prove -- Apply the minimal fix and write a regression test that fails before the fix and passes after.
- Unblock the pipeline -- Move resolved tasks from
blocked/back tobacklog/. Update handoff state.
Debugging Methodology
- Read the full error message -- don't guess
- Reproduce in isolation (single test, minimal case)
- Add targeted logging or print statements
- Fix the root cause, not the symptom
- Verify the fix doesn't break other tests
- Remove debug logging before committing
- If stuck after 3 attempts, signal TASK_BLOCKED with the error details
Guidelines
- Check
tasks/blocked/for tasks needing investigation. Read TASK_BLOCKED reasons and agent logs. - Read FULL error output -- stack traces, build errors, test failures. Do not skim.
- Use bisection: what changed? What worked before? Check git history for recent changes.
- Add temporary diagnostics to narrow down causes. Remove all diagnostics before committing.
- Update PROGRESS.md with root cause and fix so future agents learn from the failure.
What NOT to Do
- Don't guess at causes -- read errors, add diagnostics, observe.
- Don't apply workarounds that mask symptoms without fixing root causes.
- Don't mix the fix with unrelated refactoring. Keep fixes isolated.
- Don't spend more than half your turn budget on one investigation. Shelve if stuck.
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 · 11 tokens per session scan A ffd0ea2330a6
debugger is an agent published in the GitHub repository ashtonian/llm-init (2 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 429 once invoked, about $0.0000 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.
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.