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/rex/mcp-rancher/debuggergit clone --depth 1 https://github.com/rex/mcp-rancherWhat 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 | $0.00029 | $0.00296 |
| Opus 5 | $0.00015 | $0.00148 |
| Sonnet 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- debugger — 100% identical, 0 lines differ
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.
- yesterday 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 6d ago), licensed MIT. It adds 29 tokens to every session and 296 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
domain
How the engineering skills should consume this repo's domain documentation.
triage-labels
The engineering skills use five canonical triage roles. This file maps those roles to the label strings used in this repo's GitHub Issues.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
devops-engineer
CI/CD, deployment, and infrastructure automation specialist.
expert-nextjs-developer
Expert Next.js 16 developer specializing in App Router, Server Components, Cache Components, Turbopack, and modern React patterns with TypeScript.
debugger
Use PROACTIVELY for errors, stack traces, test failures, or unexpected behavior. Root-cause analysis + minimal fix.