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 Eliyce/paqad-ai --skill root-cause-analysisgit clone --depth 1 https://github.com/Eliyce/paqad-aiWrote 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/eliyce/paqad-ai/root-cause-analysis)<a href="https://agentmods.dev/skills/eliyce/paqad-ai/root-cause-analysis"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/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/eliyce/paqad-ai/root-cause-analysis"><img src="https://agentmods.dev/badge/skills/eliyce/paqad-ai/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.00016 | $0.00474 |
| Opus 5 | $0.00008 | $0.00237 |
| Sonnet 5 | $0.00003 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00047 |
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 8d 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
What It Does
Produces a canonical root cause analysis document with a fixed section set so investigations stay comparable across stacks and incidents.
Use This When
Use this when the workflow is explicitly root-cause-analysis and the team needs a durable artifact that captures the problem, evidence, root cause, and solution in one place.
Inputs
- Read the incoming problem statement first.
- Read the current stack snapshot, logs, traces, tests, or incident notes when available.
- Use stack-specific tools and rules only as investigation inputs, not as a reason to vary the RCA structure.
Procedure
- Restate the problem clearly and identify the affected stack context.
- Capture symptoms, impact, and timeline evidence before writing a conclusion.
- Separate confirmed root causes from contributing factors and open questions.
- Record the remediation in the
Solutionsection even when it is proposed rather than already deployed. - End with verification steps and follow-up actions needed to prevent recurrence.
Output Contract
- Match
assets/output.template.mdexactly: 8 canonical sections in the order fromassets/section-order.txt. ## Solutionis always present, even when the remediation is proposed not deployed.- Output must pass
scripts/lint-output.sh(exit 0) — it enforces the section order strictly.
Escalate / Stop Conditions
- Ask when there is not enough evidence to distinguish root cause from speculation.
- Warn when the available evidence conflicts across logs, tests, or runtime observations.
- Do not present a guess as a confirmed root cause.
Resources
references/rca-sections.mdscripts/lint-output.shassets/output.template.mdassets/section-order.txtagents/openai.yaml
What ships with it
5 files 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.
- 8d ago First seen · 63 lines · 16 tokens per session scan A 2c6ec10162a5
root-cause-analysis is a skill published in the GitHub repository Eliyce/paqad-ai (8 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 474 once invoked, about $0.0001 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 skills, from other repositories
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
auto-fix
A bug-fixing workflow that first reproduces a problem with a test, then applies the smallest code change needed. It also checks the related code path and runs tests afterward.
environment-diagnostics
Environment variable validation and configuration verification. Checks that required variables are set, config files parse correctly, ports are available, and system dependencies meet version requirements.
debugging
A structured method for finding and fixing software bugs. It starts by writing a test that reproduces the failure, then investigates its underlying cause before making a small fix.
ast-refactoring
A code-refactoring guide that uses an abstract syntax tree, a structured representation of source code, to make changes based on code meaning rather than text matching.
entropy-scan
A codebase health scan that measures disorder and highlights technical debt, meaning code problems that make future changes slower or riskier. It checks complexity, dependencies, repeated code, file size, and recent change frequency.