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/NikiforovAll/claude-code-rulesWrote 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/nikiforovall/claude-code-rules/root-cause-analyst)<a href="https://agentmods.dev/agents/nikiforovall/claude-code-rules/root-cause-analyst"><img src="https://agentmods.dev/badge/agents/nikiforovall/claude-code-rules/root-cause-analyst/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/nikiforovall/claude-code-rules/root-cause-analyst"><img src="https://agentmods.dev/badge/agents/nikiforovall/claude-code-rules/root-cause-analyst.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.00174 |
| Opus 5.5 | $0.00009 | $0.00070 |
| Sonnet 5.5 | $0.00005 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
root-cause-analyst 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 12d 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
95% identical to root-cause-analyst — 44 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
Root Cause Analyst
Find the underlying cause, not just the symptom. Keep several hypotheses open and test each against evidence (code, logs, data). Mark anything you could not verify as a hypothesis, and say where evidence contradicts a theory.
Important Guidelines
- Use Explore SubAgent: Use built-in @agent-Explore to explore existing codebase when needed
Report
The root cause with its evidence chain and a confidence level, the blast radius, and remediation options with trade-offs. When the caller's brief defines a report shape, use that.
Do not change code unless the caller asks. The caller decides on the fix after reading your report.
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.
- 12d ago Changed · -34 lines 9c7d845d405a
- 24d ago First seen · 53 lines · 23 tokens per session scan A 3e599d297484
root-cause-analyst is an agent published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 12d ago), licensed Apache-2.0. It adds 23 tokens to every session and 174 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to root-cause-analyst, differing in 44 lines, and is treated as a copy.
Other agents, from other repositories
dead-code-analyzer
Analyzes the codebase to find unused code — functions, imports, exports, variables, types, and classes — and produces a cleanup report with confidence levels. Never auto-deletes; reports findings for user review. Context: User wants to find unused code user: "find dead code" Context: User asks about code hygiene user…
queue-debugger
Use this agent when the user encounters "queue not delivering messages", "consumer errors", "DLQ filling up", "throughput issues", "message backlog", "queue timeout errors", or needs systematic Cloudflare Queues troubleshooting. Examples.
d1-debugger
Autonomous diagnostic agent that investigates Cloudflare D1 database issues through 9-phase analysis (config, migrations, queries, bindings, errors, limits, performance, Time Travel, report). Use when encountering D1 query errors, migration failures, binding issues, performance degradation, or limit/quota errors.
do-debugger
Autonomous Durable Objects debugger. Automatically detects and fixes DO configuration errors, runtime issues, and common mistakes without user intervention.
Turnstile CSP Debugger
This agent should be used when the user asks to "validate CSP for turnstile", "fix CSP errors", "check content security policy", or encounters error 200500. Analyzes Content Security Policy headers and suggests Turnstile-compatible configurations.
troubleshooting-agent
This agent should be used when the user asks to "debug Cloudflare Images errors", "troubleshoot upload failures", "diagnose CORS issues", "fix transformation errors", or encounters errors 5408, 9401-9413, multipart/form-data encoding issues, or API connectivity problems.