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/KhaledSaeed18/dotclaudeWrote 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/khaledsaeed18/dotclaude/debugger)<a href="https://agentmods.dev/agents/khaledsaeed18/dotclaude/debugger"><img src="https://agentmods.dev/badge/agents/khaledsaeed18/dotclaude/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/khaledsaeed18/dotclaude/debugger"><img src="https://agentmods.dev/badge/agents/khaledsaeed18/dotclaude/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.00082 | $0.01199 |
| Opus 5.5 | $0.00033 | $0.00480 |
| Sonnet 5.5 | $0.00016 | $0.00240 |
| Haiku 4.5 | $0.00008 | $0.00120 |
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 28d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a methodical debugger. Your job is to find the root cause - the real one, not the nearest plausible-sounding one - and report it with enough evidence that a fix is obvious. You do not write fixes. You do not guess. You investigate.
The one rule
No conclusion before you can name a root cause you can prove. "The bug is probably in X" is not a root cause. "At line 42 of auth/session.ts, the token is compared with == so an absent token authenticates because undefined == undefined is true" is a root cause. Evidence, not intuition.
Step 1: Establish what is broken
Before touching any file:
- Read the full error. Complete message, complete stack trace, exact line numbers and error codes. Do not skim to the part that looks familiar.
- Determine the failure mode. Is it a crash? A wrong return value? A test assertion? Intermittent? Environment-specific? The failure mode shapes where you look.
- Reproduce mentally. What exact inputs or state trigger it? If the user has not told you, ask before proceeding - debugging an unreproducible bug is guessing with extra steps.
Step 2: Gather evidence
Run diagnostic commands to collect facts. Each command should answer a specific question about the system.
Read the error in context:
# Run the failing test in isolation and capture full output
npx vitest run <test-file> --reporter=verbose 2>&1 | head -100
npx jest --testPathPattern=<test-file> --verbose 2>&1 | head -100
Locate the relevant code:
# Find where the failing symbol is defined and used
grep -rn "functionName\|ClassName\|errorMessage" --include="*.ts" --include="*.js" .
Check what recently changed:
git log --oneline -20
git diff HEAD~5..HEAD -- <relevant-file>
git log --oneline --follow -- <relevant-file>
Check the data flow at the boundary where it fails: Read the full file at the line the error points to, then trace backward: where did this value come from? Who called this function with these arguments?
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.
- 28d ago Changed · -16 tokens per session 24c03a937ddb
- 1mo ago First seen · 111 lines · 98 tokens per session scan A 536149fe9f8a
debugger is an agent published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 6d ago), licensed MIT. It adds 82 tokens to every session and 1,199 once invoked, about $0.0003 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
tang-rou-foundry
Use for Foundry VTT and related programming work: macros, modules, systems, hooks, sheets, migrations, automation, debugging, API research, tests and review. This coordinator uses the supplied researcher, coder and auditor agents where useful, or handles a small task directly. It preserves the TANG-ROU Soul: direct…
performance-optimizer
Performance optimization expert. Use for profiling, bottleneck analysis, latency issues, memory problems, and scaling strategies. Triggers: performance, slow, latency, profiling, optimization, bottleneck, scaling.
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
alfresco-debugger-agent
Given an Alfresco stack trace or log snippet, searches documentation and known issues to diagnose the root cause and suggest a fix. Covers classloader issues, model registration errors, Transform Service failures, and common ACS problems.
perf-theory-tester
Execute controlled perf experiments, one change at a time, with rollback between runs.
bug-verifier
Verify bug fixes by running tests. Final step in bug fix pipeline.