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 skills/leifericf/agentic-sdk/analyze-root-causenpx skills add leifericf/agentic-sdk --skill analyze-root-causegit clone --depth 1 https://github.com/leifericf/agentic-sdkWrote 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/leifericf/agentic-sdk/analyze-root-cause)<a href="https://agentmods.dev/skills/leifericf/agentic-sdk/analyze-root-cause"><img src="https://agentmods.dev/badge/skills/leifericf/agentic-sdk/analyze-root-cause.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.00014 | $0.00442 |
| Opus 5 | $0.00007 | $0.00221 |
| Sonnet 5 | $0.00003 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
analyze-root-cause 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 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.
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
analyze-root-cause
Trace the full causal chain from trigger to failure, identify defense gaps, and define preventative controls. Anchor on one precise, falsifiable failure mode.
Procedure
- Anchor on one primary failure mode and a minimal, falsifiable problem statement; link secondary failures to it.
- Gather context, at most three questions, preferring binary (validate each causal link) and pick-one (select the most plausible chain branch).
- Write a one- to three-sentence precise problem statement.
- Document customer impact: what users experienced, duration, blast radius.
- Trace the causal chain backward from failure to root trigger; number each step.
- Apply Five Whys if the chain has not reached a systemic root.
- Technical deep dive: components involved, data shapes, the exact breakage, and why tests, monitoring, and process did not catch it.
- Document reproduction: preconditions, steps, expected versus actual.
- Summarize the fix applied and the follow-up hardening needed.
- Define preventative controls, each with type (test, monitoring, process, architecture), what it prevents, how to verify it, and owner.
- Assess residual risk and why it is acceptable.
- Write
~/.agentic-sdk/<project>/artifacts/ops/YYYY-MM-DD_rca_<incident_slug>.mdwith: Metadata, Problem Statement, Customer Impact, Causal Chain, Five Whys (optional), Technical Deep Dive, Reproduction Notes, Fix Summary, Preventative Controls, Residual Risk, Open Questions. Slug: lowercase, hyphens, descriptive.
Boundaries
Owns the causal chain and preventative controls. review-incident owns the blameless incident review; assess-risk owns pre-deployment release risk. Reached by investigate.
Return
One line: the artifact written, the root cause, and the top preventative
control, or blocked: <reason>.
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 · 47 lines · 14 tokens per session scan A c15f9a94d510
analyze-root-cause is a skill published in the GitHub repository leifericf/agentic-sdk (5 stars, last pushed 3d ago), licensed MIT. It adds 14 tokens to every session and 442 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…