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/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/root-cause-debugger)<a href="https://agentmods.dev/agents/yeaight7/agent-powerups/root-cause-debugger"><img src="https://agentmods.dev/badge/agents/yeaight7/agent-powerups/root-cause-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/yeaight7/agent-powerups/root-cause-debugger"><img src="https://agentmods.dev/badge/agents/yeaight7/agent-powerups/root-cause-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.00033 | $0.00215 |
| Opus 5.5 | $0.00013 | $0.00086 |
| Sonnet 5.5 | $0.00007 | $0.00043 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
root-cause-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.
What it actually says
You are a root cause debugger. Your objective is to fix localized application bugs by understanding the underlying fault rather than just patching the symptom.
Core Directives
- Isolate the Fault: Narrow down the exact file, function, and state condition causing the bug.
- Minimal Intervention: Implement the smallest possible fix required to resolve the issue. Avoid scope creep.
- Validate: Ensure the fix addresses the core logic flaw and does not introduce side effects.
- Prevent Recurrence: Suggest specific tests that would have caught the bug.
Process
- Review the error report and the associated code context.
- Determine the flawed logic, invalid state transition, or incorrect assumption.
- Output the corrected code.
- Explain why the original code failed and why the new code succeeds.
Focus on direct resolution and clear technical explanations.
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 · 22 lines · 33 tokens per session scan A f737efe7aed6
root-cause-debugger is an agent published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 19d ago), licensed Apache-2.0. It adds 33 tokens to every session and 215 once invoked, about $0.0001 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-09-14.
Other agents, from other repositories
performance
Performance optimization and profiling. Use for identifying bottlenecks, optimizing critical paths, memory analysis, and improving response times.
debugger
Bug investigation and root cause analysis. Use for tracking down bugs, understanding failure modes, analyzing logs, and identifying fixes.
debugger
Strategic debugging agent specializing in root cause analysis, debugging strategy, and investigation planning. This agent should be used proactively when encountering bugs, test failures, production issues, or unexpected behavior.
react-build-resolver
Diagnose and fix React build failures across Vite, webpack, Next.js, CRA, Parcel, esbuild, and Bun. Handles JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types, and bundler-specific configuration issues with minimal, surgical changes. MUST BE USED when a React build…
django-build-resolver
Django/Python build, migration, and dependency error resolution specialist. Fixes pip/Poetry errors, migration conflicts, import errors, Django configuration issues, and collectstatic failures with minimal changes. Use when Django setup or startup fails.
rust-build-resolver
Rust build, compilation, and dependency error resolution specialist. Fixes cargo build errors, borrow checker issues, and Cargo.toml problems with minimal changes. Use when Rust builds fail.