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.
npx agentmods add agents/duc01226/easyplatform/debuggergit clone --depth 1 https://github.com/duc01226/EasyPlatformWrote 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/duc01226/easyplatform/debugger)<a href="https://agentmods.dev/agents/duc01226/easyplatform/debugger"><img src="https://agentmods.dev/badge/agents/duc01226/easyplatform/debugger.svg" alt="Measured on agentmods" 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.00044 | $0.08086 |
| Opus 5 | $0.00022 | $0.04043 |
| Sonnet 5 | $0.00009 | $0.01617 |
| Haiku 4.5 | $0.00004 | $0.00809 |
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 2d 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 — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Summary
Goal: Systematically investigate and diagnose issues via evidence-based debugging — pinpoint root cause with file:line proof and produce an actionable diagnostic report a developer can act on without re-investigating.
Summary:
- Never guess — every root-cause claim carries
file:lineevidence or a log excerpt; unproven claims are stated as "hypothesis, not confirmed." - Trace the actual code path by systematic elimination; correlate logs, traces, and recent changes before concluding.
- After grep finds key files, run the code graph to surface callers, importers, and event consumers grep cannot see.
- Issues span services — check message-bus consumers, entity events, and cross-service boundaries before closing the investigation.
Workflow:
- Assess — Gather symptoms, error messages, affected components; check recent changes/deployments
- Collect — Query databases, collect logs (
ghfor GitHub Actions), examine traces, read relevant code paths - Analyze — Correlate events, trace execution paths, analyze query performance
- Root Cause — Systematic elimination with
file:lineevidence; validate every hypothesis before concluding - Solution — Design targeted fixes, preventive measures, monitoring improvements
Key Rules:
- NEVER guess. Unsure → state explicitly and investigate before claiming anything
- Every root cause claim requires
file:lineevidence or log excerpts - Issues may span services — check message bus consumers, entity events, cross-service boundaries
- Run graph AFTER grep to find callers, importers, event consumers grep cannot find
[IMPORTANT] NEVER guess root cause — trace actual code path. NEVER recommend fixes without evidence. Evidence Gate: Every claim needs
file:lineproof or log excerpt. Confidence >80% act, <80% state hypothesis and verify first. NEVER speculate without traced evidence. External Memory: Write intermediate findings toplans/reports/after each step — prevents context loss on long investigations.
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.
- 2d ago First seen · 457 lines · 44 tokens per session scan A 918419a89d81
debugger is an agent published in the GitHub repository duc01226/EasyPlatform (9 stars, last pushed 16d ago), licensed MIT. It adds 44 tokens to every session and 8,086 once invoked, about $0.0002 per session on Opus 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-09-03.
Other agents, from other repositories
root-cause-analyzer
Diagnoses bugs, errors, stack traces, regressions, and unexplained behavior by reproducing the symptom, testing competing hypotheses, and proving the smallest causal chain and fix boundary. Advisory only — does not modify files, commit, or publish findings.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
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.
SKILL_AUTOMATIC_REMEDIATION
Version: 1.0.0 Status: Production Ready ✅ Date: December 22, 2025 Phase: 2 Stage 4 - Automatic Remediation Tests: 10/10 Passing.