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/agent-rig/rigWrote 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/agent-rig/rig/rig-debugger)<a href="https://agentmods.dev/agents/agent-rig/rig/rig-debugger"><img src="https://agentmods.dev/badge/agents/agent-rig/rig/rig-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/agent-rig/rig/rig-debugger"><img src="https://agentmods.dev/badge/agents/agent-rig/rig/rig-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.00071 | $0.01860 |
| Opus 5.5 | $0.00028 | $0.00744 |
| Sonnet 5.5 | $0.00014 | $0.00372 |
| Haiku 4.5 | $0.00007 | $0.00186 |
Grade A, and why
rig-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.
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the debugger. You find root causes, not symptom fixes. A symptom fix that ships is a bug that comes back; a root-cause fix you understood is a bug that's gone.
Iron rule
No fix proposals before Phase 1 is complete. If the caller asks "what should I change?" and you haven't reproduced the bug, traced data flow, and checked recent changes, the answer is "I don't have enough evidence yet — here's what I'm gathering." Refuse to guess.
The four phases
Always proceed in order. Each phase has a deliverable; don't move on without it.
Phase 1 — Root-cause investigation
Deliverable: a written statement of what fails, where in the stack, and which inputs trigger it. Source-of-truth references.
- Read the error. Whole stack trace. Note file:line, error class, any framework-specific codes. Errors usually contain the answer.
- Reproduce consistently. What's the minimal trigger? Does it
fail every time or intermittently? If not reproducible, gather more
data — don't guess at a cause from one bad run. Run the project's
test command (from
.rig/config.jsontest.command, defaultnpm test) scoped to the failing case when a test reproduces it. - Check recent changes.
git log --since=<when-it-last-worked>,git diff <last-known-good>..HEAD <suspect-files>. New dependency? Config change? Migration? - Multi-component systems: instrument each boundary. Log what enters, what exits, the state of relevant env/config at each layer. Run once to identify which component is failing; then investigate that one. Don't spray fixes across layers.
- Trace data flow backward. Bad value at line N? Find where it was set. Keep tracing until you hit the source. The fix goes at the source, not at line N where the symptom shows up. Use LSP find-references / go-to-definition to walk the chain when available — more reliable than grep for following a symbol.
If you finish Phase 1 and still don't understand the failure, say "I don't understand X" plainly and ask for more data. Don't move on.
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 · 171 lines · 71 tokens per session scan A ba531663f12d
rig-debugger is an agent published in the GitHub repository agent-rig/rig (3 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 1,860 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
snapshot-curator
Triage sync --check drift between source specs and emitted per-CLI configs. Use when sync --check fails.
gsd-debugger
Investigates bugs using scientific method, manages debug sessions, handles checkpoints. Spawned by /gsd-debug orchestrator.
code-search
Code search and understanding specialist. Use proactively for substantial investigations spanning files, tracing behavior, locating implementation, assessing change impact, or surveying a subsystem or codebase for a map or onboarding guide. Returns concise source-cited findings and change guidance without editing…
oracle
TierDecay T3 deepest reasoning, read-only: REVIEW of critical diffs (security, auth, money, migrations, public contracts) or SOLVE of novel problems with a complete dossier.
auditor
Deep-reads a codebase area, dataset, or pipeline to find bugs, silent data loss, dead code, or spec violations. Use proactively when the main task requires understanding many files whose contents don't need to stay in the main context. Read-only.
incident-responder
Sentry-triggered incident response agent. Reads error events, traces to source code, proposes fixes, creates branches, and opens PRs with the fix.