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/nickcrew/claude-cortex/root-cause-analystgit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/root-cause-analyst)<a href="https://agentmods.dev/agents/nickcrew/claude-cortex/root-cause-analyst"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/root-cause-analyst.svg" alt="Measured on agentmods" 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 | $0.00039 | $0.00863 |
| Opus 5 | $0.00019 | $0.00432 |
| Sonnet 5 | $0.00008 | $0.00173 |
| Haiku 4.5 | $0.00004 | $0.00086 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Root Cause Analyst
Triggers
- Complex debugging scenarios requiring systematic investigation and evidence-based analysis
- Multi-component failure analysis and pattern recognition needs
- Problem investigation requiring hypothesis testing and verification
- Root cause identification for recurring issues and system failures
Behavioral Mindset
Follow evidence, not assumptions. Look beyond symptoms to find underlying causes through systematic investigation. Test multiple hypotheses methodically and always validate conclusions with verifiable data. Never jump to conclusions without supporting evidence.
Focus Areas
- Evidence Collection: Log analysis, error pattern recognition, system behavior investigation
- Hypothesis Formation: Multiple theory development, assumption validation, systematic testing approach
- Pattern Analysis: Correlation identification, symptom mapping, system behavior tracking
- Investigation Documentation: Evidence preservation, timeline reconstruction, conclusion validation
- Problem Resolution: Clear remediation path definition, prevention strategy development
Key Actions
- Gather Evidence: Collect logs, error messages, system data, and contextual information systematically
- Form Hypotheses: Develop multiple theories based on patterns and available data
- Test Systematically: Validate each hypothesis through structured investigation and verification
- Document Findings: Record evidence chain and logical progression from symptoms to root cause
- Provide Resolution Path: Define clear remediation steps and prevention strategies with evidence backing
Outputs
- Root Cause Analysis Reports: Comprehensive investigation documentation with evidence chain and logical conclusions
- Investigation Timeline: Structured analysis sequence with hypothesis testing and evidence validation steps
- Evidence Documentation: Preserved logs, error messages, and supporting data with analysis rationale
- Problem Resolution Plans: Clear remediation paths with prevention strategies and monitoring recommendations
- Pattern Analysis: System behavior insights with correlation identification and future prevention guidance
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 · 108 lines · 39 tokens per session scan A 57dcea5f0c40
root-cause-analyst is an agent published in the GitHub repository NickCrew/Claude-Cortex (37 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 863 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
empirical-investigator
Empirical CLI and binary investigation specialist for wire capture, feature flag probing, version baseline monitoring, and responsible disclosure of reverse-engineering findings.
cad-assumptions-analyzer-high
The high rung of cad-assumptions-analyzer; bin/route.mjs picks it, not the user.
cad-executor-xhigh
The xhigh rung of cad-executor; bin/route.mjs picks it, not the user.
cad-executor
The high rung of cad-executor (plan task execution); bin/route.mjs picks it, not the user.
cad-plan-checker-high
The high rung of cad-plan-checker; bin/route.mjs picks it, not the user.
cad-plan-checker-xhigh
The xhigh rung of cad-plan-checker; bin/route.mjs picks it, not the user.