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 yindia/rootcause --skill k8s-incidentgit clone --depth 1 https://github.com/yindia/rootcauseWrote 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/yindia/rootcause/k8s-incident)<a href="https://agentmods.dev/skills/yindia/rootcause/k8s-incident"><img src="https://agentmods.dev/badge/skills/yindia/rootcause/k8s-incident.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.1 | $0.00000 | $0.02407 |
| Opus 5 | $0.00000 | $0.01203 |
| Sonnet 5 | $0.00000 | $0.00481 |
| Haiku 4.5 | $0.00000 | $0.00241 |
Grade A, and why
k8s-incident 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.
How it starts
The opening of the file, as written. The whole thing — 402 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: k8s-incident
Incident response workflow for Kubernetes outages using RootCause MCP tools only.
Primary goal: stabilize service fast, preserve evidence, then explain likely causes.
Core Response Sequence
Follow this exact order unless evidence forces a branch:
- connectivity check
- baseline snapshot
- incident bundle
- change correlation
- focused debug
- event timeline
- resource pressure scan
- ranked hypotheses
Trigger Signals
Use this skill for requests like:
- service down
- outage
- high 5xx
- alert storm
- crashlooping pods
- pending pods
- sudden latency jump
- release appears to have broken traffic
Severity-Based Triage Table
| Severity | Definition | Initial Objective | First 3 Tools |
|---|---|---|---|
| SEV-1 | customer-critical outage, broad impact | restore service path within minutes | k8s.ping → k8s.overview → rootcause.incident_bundle |
| SEV-2 | major degradation, partial outage | isolate blast radius and prevent escalation | k8s.ping → rootcause.incident_bundle → rootcause.change_timeline |
| SEV-3 | localized failure, workaround exists | identify root component and schedule safe fix | k8s.overview → k8s.events_timeline → k8s.diagnose |
| SEV-4 | low urgency anomaly or warning trend | gather evidence and create prevention actions | k8s.overview → k8s.resource_usage → k8s.best_practice |
Tool Priority Matrix
| Symptom | Primary Tool | Secondary Tool | Why |
|---|---|---|---|
| API failure | k8s.ping |
k8s.context |
verify control plane reachability and context |
| unknown scope | k8s.overview |
rootcause.incident_bundle |
broad health then structured evidence |
| crash loops | k8s.crashloop_debug |
k8s.logs |
fast root signal from lifecycle and container logs |
| pending pods | k8s.scheduling_debug |
k8s.resource_usage |
scheduling blockers and node pressure |
| service unreachable | k8s.network_debug |
k8s.graph |
service chain and policy/LB blockers |
| config break | k8s.config_debug |
k8s.describe |
missing keys and mount/ref failures |
| storage mount errors | k8s.storage_debug |
k8s.events_timeline |
PVC/PV and attach sequence |
| auth/permission errors | k8s.permission_debug |
k8s.describe |
RBAC/IRSA binding and runtime failures |
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 · 402 lines · 0 tokens per session scan A f29b5dd67228
k8s-incident 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 2,407 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
k8s-service-path
Trace the Kubernetes service path — Service to selector to pods to EndpointSlices to readiness, plus Ingress routing. Use when a service is getting no traffic, an ingress is not routing, or someone asks why a workload is unreachable inside a cluster.
k8s-workload-inventory
List Kubernetes workloads and namespaces — pods with their node, phase and readiness, plus events. Use when asked what is running, where it is running, what is failing, or for a general inventory of a cluster.
kubernetes
Kubernetes operations playbook for deploying services: core objects, probes, resource sizing, safe rollouts, and fast kubectl debugging.
kubeview-debug
Debug and diagnose Kubernetes clusters using KubeView MCP server tools. Use when investigating cluster issues (pod crashes, deployment failures, service connectivity problems, node issues, resource constraints), performing cluster health checks, or troubleshooting any Kubernetes workload. Trigger phrases include…
platform-integration
Cross-layer platform integration skill covering end-to-end delivery flows, team onboarding, DORA metrics, cross-layer debugging, and platform health checks. Orchestrates across all platform layers (build, pipeline, registry, secrets, mesh, GitOps, progressive delivery) and owns gitops-promoter CRDs (PromotionStrategy…
bazel-k8s-expert
Expert knowledge for deploying Quarkus/Java applications to Kubernetes using Bazel. Covers rulesk8s, Helm, Kustomize, ConfigMaps, Secrets, and health probes.