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/yindia/rootcause/rootcause-rcanpx skills add yindia/rootcause --skill rootcause-rcagit clone --depth 1 https://github.com/yindia/rootcauseWhat 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.00000 | $0.01671 |
| Opus 5 | $0.00000 | $0.00835 |
| Sonnet 5 | $0.00000 | $0.00334 |
| Haiku 4.5 | $0.00000 | $0.00167 |
Grade A, and why
rootcause-rca 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: rootcause-rca
Full incident RCA pipeline for evidence collection, timeline analysis, root-cause drafting, remediation planning, and postmortem export.
This skill is for structured incident documentation and decision support, not for ad-hoc single-command troubleshooting.
Trigger Phrases
Use this skill when the user asks for:
- root cause analysis
- incident report
- postmortem draft
- what changed before outage
- remediation plan
- corrective and preventive actions
- timeline export
RootCause Tools Allowed
Only use these tool names in this skill:
rootcause.incident_bundlerootcause.change_timelinerootcause.rca_generaterootcause.remediation_playbookrootcause.postmortem_exportk8s.events_timelinehelm.list
RCA Pipeline Overview
Canonical sequence:
- Bundle
- Timeline
- RCA draft
- Remediation playbook
- Postmortem export
Shorthand:
bundle -> timeline -> rca -> remediation -> postmortem
Step 1: Incident Bundle
Use rootcause.incident_bundle to gather cross-tool evidence.
Recommended minimal parameters:
namespace: payments
keyword: "timeout"
includeHelm: true
includeDefaultChain: true
Useful optional parameters:
eventLimit: tune for noisy namespaces.maxSteps: cap diagnostic expansion.outputMode:bundlefor full context,timelinefor condensed view.continueOnError: keep collecting when one branch fails.
When to run again:
- evidence is too generic,
- namespace was too broad,
- keyword was not specific.
Step 2: Change Timeline
Use rootcause.change_timeline to align cluster events and release changes.
Recommended parameters:
namespace: payments
keyword: "timeout"
includeHelm: true
includeNormal: false
timelineLimit: 150
Use timeline to answer:
- What changed just before impact?
- Was there a rollout, config update, or restart wave?
- Did warning events precede customer-visible failure?
If Helm activity is expected but absent:
- run
helm.listin relevant namespace, - confirm release names and history context.
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.
- 3d ago First seen · 260 lines · 0 tokens per session scan A f5033fa10bad
rootcause-rca is a skill published in the GitHub repository yindia/rootcause (42 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,671 tokens. 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
dependabot-batch
Use when reviewing Radar's weekly Dependabot PRs and replacing the safe, 72-hour-soaked updates with one changelog-vetted, tested PR.
test-radar
Use when building and testing Radar changes with the repository's real-instance smoke-test workflow.
visual-test
Use when visually testing Radar UI changes against a real Kubernetes cluster with Playwright screenshots.
release-chart
Cut and publish a new release of the Zabbix Helm chart in this repository, following the versioning rules and maintainer release process documented in CONTRIBUTING.md and CLAUDE.md (bump Chart.yaml/artifacthub-pkg.yml/values.yaml, regenerate docs, tag the release so CI publishes it). Trigger on requests like "release…
helm
Skill "helm" from chaterm/terminal-skills, covering helm 包管理, 概述, 基础命令, 仓库管理 and 添加仓库.
bazel-k8s-expert
Expert knowledge for deploying Quarkus/Java applications to Kubernetes using Bazel. Covers rulesk8s, Helm, Kustomize, ConfigMaps, Secrets, and health probes.