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-troubleshootgit 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-troubleshoot)<a href="https://agentmods.dev/skills/yindia/rootcause/k8s-troubleshoot"><img src="https://agentmods.dev/badge/skills/yindia/rootcause/k8s-troubleshoot/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/yindia/rootcause/k8s-troubleshoot"><img src="https://agentmods.dev/badge/skills/yindia/rootcause/k8s-troubleshoot.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.00000 | $0.03359 |
| Opus 5 | $0.00000 | $0.01680 |
| Sonnet 5 | $0.00000 | $0.00672 |
| Haiku 4.5 | $0.00000 | $0.00336 |
Grade A, and why
k8s-troubleshoot 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 9d 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
k8s-troubleshoot
Comprehensive Kubernetes troubleshooting skill for pod, service, node, storage, config, and permission failures.
This skill prioritizes RootCause MCP tools in k8s.* format and avoids non-RootCause aliases.
Scope
- Diagnose unknown failures quickly with
k8s.diagnose. - Run scenario-accurate graph analysis with
k8s.debug_flow. - Pivot into specialized debuggers for crash loops, scheduling, networking, storage, config, and RBAC.
- Produce evidence-backed findings with logs, events, object status, and resource usage.
Hard Rules
- Always start from symptom -> state -> tool mapping.
- Use RootCause MCP tool names only (
k8s.logs,k8s.describe,k8s.crashloop_debug, etc.). - Never start with random object browsing when a state-specific debugger exists.
- Always collect both runtime evidence (
k8s.logs) and control-plane evidence (k8s.events_timeline). - When multiple symptoms appear, run
k8s.diagnosefirst, then chaink8s.debug_flowby scenario.
Trigger Phrases
- Pod is failing
- Pod keeps restarting
- CrashLoopBackOff
- ImagePullBackOff
- Deployment rollout stuck
- Pods pending
- Service unreachable
- 503 from ingress
- PVC not binding
- Mount failed
- Secret or config not found
- Forbidden RBAC error
- Autoscaling not working
- Node pressure or evictions
Tool Quick Map
| Need | Primary Tool | Follow-up Tools |
|---|---|---|
| Unknown or mixed symptom | k8s.diagnose |
k8s.debug_flow, k8s.events_timeline |
| Crash/restart/image pulls | k8s.crashloop_debug |
k8s.logs, k8s.describe |
| Pending/scheduling | k8s.scheduling_debug |
k8s.resource_usage, k8s.events_timeline |
| Service connectivity | k8s.network_debug |
k8s.graph, k8s.debug_flow |
| Storage failures | k8s.storage_debug |
k8s.describe, k8s.events_timeline |
| ConfigMap/Secret issues | k8s.config_debug |
k8s.describe, k8s.logs |
| RBAC/IRSA permission | k8s.permission_debug |
k8s.describe, k8s.events_timeline |
| HPA behavior | k8s.hpa_debug |
k8s.resource_usage, k8s.events_timeline |
| VPA recommendations | k8s.vpa_debug |
k8s.resource_usage, k8s.describe |
| Timeline and causality | k8s.events_timeline |
k8s.events, k8s.describe |
What ships with it
2 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.
- 9d ago First seen · 301 lines · 0 tokens per session scan A fcee9df809dd
k8s-troubleshoot 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 3,359 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
helm
A guide to Helm, a package manager for Kubernetes applications. Helm uses reusable packages called Charts to install, configure, upgrade, inspect, and remove groups of Kubernetes resources.
bazel-k8s-expert
Expert knowledge for deploying Quarkus/Java applications to Kubernetes using Bazel. Covers rulesk8s, Helm, Kustomize, ConfigMaps, Secrets, and health probes.
k8s-deployer
Kubernetes deployment management - generate manifests, Helm charts, manage rollouts, check cluster status, and apply security best practices.
k8s-ingress-gateway
A troubleshooting guide for Kubernetes Ingress and Gateway configurations. Kubernetes is a system for running containers, and Ingress and Gateway components route web traffic to those containers.
kubernetes-operator
Deploy and manage applications on Kubernetes. Covers deployments, services, ingress, HPA, secrets, and production-grade cluster configuration.
hunt-k8s
Hunt Kubernetes & Docker — API anonymous access, kubelet 10250 exec (SPDY/WebSocket, NOT plain POST) and the simpler /run primitive, etcd 2379 unauth, dashboard skip-login, RBAC misconfig, secret/SA-token abuse, docker.sock host escape, runc/container-escape (Leaky Vessels CVE-2024-21626), API-server-mediated…