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 skills add itseffi/agentic-os --skill root-cause-analysisgit clone --depth 1 https://github.com/itseffi/agentic-osWrote 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/skills/itseffi/agentic-os/root-cause-analysis)<a href="https://agentmods.dev/skills/itseffi/agentic-os/root-cause-analysis"><img src="https://agentmods.dev/badge/skills/itseffi/agentic-os/root-cause-analysis/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/skills/itseffi/agentic-os/root-cause-analysis"><img src="https://agentmods.dev/badge/skills/itseffi/agentic-os/root-cause-analysis.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.00355 |
| Opus 5.5 | $0.00009 | $0.00142 |
| Sonnet 5.5 | $0.00005 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
root-cause-analysis 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
Root Cause Analysis
Uncover root causes and explore consequences through structured questioning.
When to Use
When you need to deeply understand a problem, decision, or situation before acting.
The Process
1. Recursive "Why" Questioning
Start with the initial question and ask "Why?" repeatedly:
- Ask "Why?" at least 5 times
- Go deeper until you reach fundamental causes
- If multiple reasons emerge, explore each branch
Example:
- Why did users churn? → Onboarding was confusing
- Why was it confusing? → Too many steps
- Why too many steps? → We added features without simplifying
- Why didn't we simplify? → No ownership of onboarding experience
- Why no ownership? → Org structure doesn't align to user journey
2. Consequence Exploration
After finding root causes, explore forward:
- 1st order: Immediate consequences
- 2nd order: What results from those?
- 3rd-5th order: Downstream effects
Consider both positive and negative outcomes.
3. First Principles Check
- What fundamental truths underlie this?
- What assumptions are we making?
- What alternative perspectives exist?
- Where are the gaps in logic?
Output Format
- Root causes (the "Why?" chain)
- Consequences (1st through 5th order)
- First principles (fundamental truths, assumptions)
- Conclusion (key insights)
When Not to Use
Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 56 lines · 23 tokens per session scan A 1352267ab607
root-cause-analysis is a skill published in the GitHub repository itseffi/agentic-os (117 stars, last pushed 14d ago), licensed MIT. It adds 23 tokens to every session and 355 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-08-30.
Other skills, from other repositories
vision-expert
Specialized instructions for Z.AI Vision MCP to handle UI-to-Code and error diagnosis.
kiro-verify-completion
Verify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
openclaw-debugger
Trigger when an OpenClaw agent is broken, silent, crashing, stuck, not responding, returning empty output, or the user says "my agent is down", "agent not working", "/openclaw-debugger". Walks through the standard OpenClaw 2026.4 diagnosis checklist and prints a report.
debug-live
Guides root-cause investigations with debugging capabilities by setting breakpoints, starting a debug session, stepping through execution, inspecting variables, and tracing symptoms back to their origin. Prefer it for runtime bugs, failing tests, exceptions, crashes, hangs, wrong/null values, and unexpected output…
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.