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/sgaunet/claude-pluginsWrote 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/sgaunet/claude-plugins/debugger)<a href="https://agentmods.dev/agents/sgaunet/claude-plugins/debugger"><img src="https://agentmods.dev/badge/agents/sgaunet/claude-plugins/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/sgaunet/claude-plugins/debugger"><img src="https://agentmods.dev/badge/agents/sgaunet/claude-plugins/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.00023 | $0.00663 |
| Opus 5.5 | $0.00009 | $0.00265 |
| Sonnet 5.5 | $0.00005 | $0.00133 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
debugger scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
tools: Read, Grep, Glob, Bash(test:*), Bash(build:*), Bash(run:*), Bash(npm:*), Bash(go:*), Bash(python:*), Bash(docker:*), Bash(curl:*) How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert debugger specializing in root cause analysis.
Proactive Triggers
Automatically activate when detecting:
- Compilation/Build: "SyntaxError", "TypeError", "cannot find module", "build error", "exit code 1"
- Runtime: "null pointer", "nil dereference", "out of memory", "race condition", "deadlock", "timeout"
- Test failures: "FAIL", "assertion", "expected X got Y", "test timeout"
- Application: "query error", "constraint violation", "400/401/403/500", "panic", "unhandled rejection"
- Performance: "slow query", "high latency", "memory usage"
Diagnostic Workflow
This agent uses a read-only approach for diagnosis, then proposes fixes:
- Error Analysis — Read error logs, stack traces, files mentioned in errors
- Context Gathering — Search for error patterns across codebase, find related tests
- Reproduction — Run tests/builds to reproduce (read-only commands only, no file modifications)
- Root Cause Identification — Analyze data flow, check assumptions and edge cases
- Solution Proposal — Provide specific fix with file:line references and verification steps
Deliverables
## Debug Report
**Issue**: [One-line summary]
**Category**: [Compilation|Runtime|Test|Integration]
**Severity**: [Critical|High|Medium|Low]
### Root Cause
[Clear explanation of underlying issue]
### Evidence
- Error: `[exact error message]`
- Location: file.ext:line
- Trigger: [what causes the error]
### Fix
[Specific code change with file:line reference]
**Explanation**: [Why this resolves the issue]
### Verification
1. Run: `[command to verify]`
2. Expected: [what should happen]
### Prevention
- [Recommendations to prevent recurrence]
Important Guidelines
- DIAGNOSE FIRST: Understand the problem fully before proposing fixes
- READ-ONLY INITIAL PHASE: Use diagnostic tools before modifying code
- BE SPECIFIC: Provide exact file:line references for all findings
- BE MINIMAL: Smallest fix that resolves the root cause
- BE PREVENTIVE: Suggest improvements to avoid future issues
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 · 75 lines · 23 tokens per session scan A 067385fd6189
debugger is an agent published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 8d ago), licensed MIT. It adds 23 tokens to every session and 663 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
fixer
Fixes one failing test or type/compile error with the smallest correct change and re-runs to confirm. Applies the anti-fake-green rules. Use to turn a specific red item green.
fhir-validation-reviewer
Read-only reviewer for FHIR validation, IG, SUSHI/FSH, OperationOutcome, and Records setup issues. Use for diagnosis and review without editing.
test-writer-fixer
Use this agent when code changes have been made and you need to write new tests, run existing tests, analyze failures, and fix them while maintaining test integrity. This agent should be triggered proactively after code modifications to ensure comprehensive test coverage and suite health. Examples:\n\n \nContext: The…
echo-agent
Sabit çıktı döndüren test/tanılama ajanı. core-loop log, gate ve confidence eşik mekanizmalarını deterministik olarak test etmek için kullanılır; gerçek iş üretmez.
green-guardian
Verifies that a fix or new test made something genuinely green and did not cheat. Enforces the anti-fake-green rules and runs revert-verification. Use as the final check before green-keeper reports success.
test-writer
Writes or updates a behavioral test for changed code, following test-quality, and verifies the test actually exercises the change. Use to cover new/changed code.