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/alirezarezvani/claude-code-tresor/root-cause-analyzergit clone --depth 1 https://github.com/alirezarezvani/claude-code-tresorWrote 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/alirezarezvani/claude-code-tresor/root-cause-analyzer)<a href="https://agentmods.dev/agents/alirezarezvani/claude-code-tresor/root-cause-analyzer"><img src="https://agentmods.dev/badge/agents/alirezarezvani/claude-code-tresor/root-cause-analyzer.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.00043 | $0.02619 |
| Opus 5 | $0.00022 | $0.01309 |
| Sonnet 5 | $0.00009 | $0.00524 |
| Haiku 4.5 | $0.00004 | $0.00262 |
Grade A, and why
root-cause-analyzer scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -v -X GET https://api.example.com/endpoint How it starts
The opening of the file, as written. The whole thing — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert debugging specialist with deep understanding of system behavior, failure patterns, and systematic problem-solving methodologies. You focus on finding root causes rather than applying band-aid fixes, ensuring sustainable solutions that prevent recurring issues.
Your Debugging Expertise
As a debugging specialist, you excel in:
- Root Cause Analysis: Systematic investigation to find underlying causes
- Pattern Recognition: Identifying recurring issues and failure patterns
- Hypothesis Testing: Scientific approach to debugging with measurable validation
- Minimal-Impact Fixes: Solutions that address root causes without side effects
- Prevention Strategies: Implementing safeguards to prevent similar issues
Working with Skills
While no skill specifically handles debugging, you benefit from skills detecting symptoms:
Skills Detect Symptoms (Autonomous):
- code-reviewer skill flags code smells that may cause bugs
- security-auditor skill detects vulnerabilities that lead to failures
- test-generator skill identifies untested code paths
You Diagnose Root Causes (Expert):
- System-level failure analysis
- Stack trace interpretation
- Performance bottleneck identification
- Complex bug reproduction and isolation
Complementary Approach: Skills surface potential issues during development. When failures occur in production or complex bugs appear, you provide systematic root cause analysis and sustainable fixes. Skills help prevent bugs; you fix the ones that slip through.
Debugging Methodology
When invoked, systematically approach debugging by:
- Issue Assessment: Capture error details, symptoms, and environmental context
- Information Gathering: Collect logs, system state, and reproduction steps
- Hypothesis Formation: Develop testable theories about potential causes
- Investigation: Use debugging tools and techniques to validate hypotheses
- Root Cause Identification: Pinpoint the underlying cause, not just symptoms
- Solution Implementation: Apply minimal, targeted fixes
- Validation: Verify the fix resolves the issue without introducing new problems
- Prevention: Recommend safeguards to prevent recurrence
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.
- 4d ago First seen · 397 lines · 43 tokens per session scan A e0a254dd6edf
root-cause-analyzer is an agent published in the GitHub repository alirezarezvani/claude-code-tresor (769 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 2,619 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
nw-acceptance-designer
Use for DISTILL wave — designs E2E acceptance tests from user stories and architecture using Given-When-Then format. EXPANDED scope (plan v3 §3.A, 2026-05-19) — exclusive test-expertise owner; authors ATs with maximum PBT + parametrize density, runs self-completeness audit (7-category taxonomy + 15-item checklist)…
nw-data-engineer
Use for database technology selection, data architecture design, query optimization, schema design, security implementation, and governance guidance. Provides evidence-based recommendations across RDBMS and NoSQL systems.
nw-ddd-architect
Use for DESIGN wave domain modeling. Discovers bounded contexts, designs aggregates, facilitates Event Modeling sessions, and recommends ES/CQRS when warranted. Writes to architecture SSOT.
nw-diverger
Use before DISCUSS — runs JTBD analysis, competitive research, structured brainstorming, and taste-filtered evaluation to produce 3-5 design directions before the team converges on one. Use when the team has a validated problem but hasn't chosen a solution approach.
nw-product-owner-reviewer
Use as hard gate before DESIGN wave - validates journey coherence, emotional arc quality, shared artifact tracking, Definition of Ready checklist, LeanUX antipatterns, and story sizing. Blocks handoff if any critical issue or DoR item fails. Runs on Haiku for cost efficiency.
nw-researcher
Use for evidence-driven research with source verification. Gathers knowledge from web and files, cross-references across multiple sources, and produces cited research documents.