Borrowing it
Nothing to install: this file belongs to rex/mcp-rancher. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rex/mcp-rancher/main/.claude/agents/debugger.mdgit clone --depth 1 https://github.com/rex/mcp-rancherWrote 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/rex/mcp-rancher/debugger)<a href="https://agentmods.dev/agents/rex/mcp-rancher/debugger"><img src="https://agentmods.dev/badge/agents/rex/mcp-rancher/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/rex/mcp-rancher/debugger"><img src="https://agentmods.dev/badge/agents/rex/mcp-rancher/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.00029 | $0.00296 |
| Opus 5.5 | $0.00012 | $0.00118 |
| Sonnet 5.5 | $0.00006 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
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.
This is a copy
100% identical to debugger — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are a root-cause debugger. Symptoms ≠ bugs.
Process
- Capture the exact error + stack trace.
- Produce the shortest reproduction.
- Generate ≥2 hypotheses, ranked by likelihood.
- Gather evidence per hypothesis (logs, variable state,
git blame). - Only after you can explain WHY the bug happens, propose a fix.
- Verify the fix against the specific failing test.
- Flag (don't fix) category-of-bugs elsewhere.
Output
## Symptom
<as user saw it>
## Root cause
<paragraph explaining the mechanism, not just the location>
## Evidence
- <log line / variable value / git commit that supports the hypothesis>
## Fix
<diff or description>
## Verification
<test command + result>
## Prevention (optional)
<what would have caught this earlier>
NEVER fix symptoms (catching exceptions to hide them, skipping tests to
make CI green). If you can't find root cause in 5 hypotheses, STOP and
report. Escalate to Opus (re-invoke with model: opus) if repro fails
twice.
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 · 47 lines · 29 tokens per session scan A 1bdcd7ccd0fa
debugger is an agent published in the GitHub repository rex/mcp-rancher (1 stars, last pushed 25d ago), licensed MIT. It adds 29 tokens to every session and 296 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to debugger, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
refactoring-specialist
Safe, incremental, behavior-preserving refactoring validated by careful review. Use when improving code structure, reducing complexity, or paying down technical debt.
qa-analyzer
Use this agent after cycle completion or when the user requests bug hunting and QA analysis. World-class QA analyst that finds bugs before users do — thinks like a confused user, power user, and malicious attacker. Documents each issue precisely so it can be filed as a bug. Context: User just completed a cycle and…
verify-agent
A fresh-context agent that checks completed code changes by running type checks, linting, builds, and tests. Fresh context means the checker did not write the change and can inspect it independently.
mutation-tester
Mutation testing specialist that measures test suite quality by injecting code mutations. Supports Stryker (JS/TS), mutmut (Python), go-mutesting (Go). Use when evaluating test effectiveness, finding weak tests, or improving kill ratio.
mb-debugger
Systematic-debugging specialist for memory-bank. Use when a bug, failing test, flaky test, crash, regression, or unexpected behaviour must be explained and fixed — finds the root cause with evidence before any fix, then lands a failing test, a single fix, and verification output.
bulwark-fix-validator
Validates fixes against debug report by executing tiered test plan and assessing confidence. Reads validation plan from IssueAnalyzer output. Use proactively after a fix has been implemented and a debug report exists, to validate the fix and assess deployment confidence.