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/k8s-diagnosticsnpx skills add yindia/rootcause --skill k8s-diagnosticsgit 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-diagnostics)<a href="https://agentmods.dev/skills/yindia/rootcause/k8s-diagnostics"><img src="https://agentmods.dev/badge/skills/yindia/rootcause/k8s-diagnostics.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.00000 | $0.02518 |
| Opus 5 | $0.00000 | $0.01259 |
| Sonnet 5 | $0.00000 | $0.00504 |
| Haiku 4.5 | $0.00000 | $0.00252 |
Grade A, and why
k8s-diagnostics 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.
How it starts
The opening of the file, as written. The whole thing — 492 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: k8s-diagnostics
Cluster and workload diagnostics playbook using RootCause MCP tool names.
Focus areas:
- cluster health assessment
- resource usage and pressure
- event chronology
- HPA and VPA behavior
- best-practice interpretation
- capacity planning
Objective
Produce evidence-backed health posture and action priorities.
This skill is mostly read-first.
If remediation requires mutation, hand off to k8s-operations.
Primary Tool Set
k8s.contextk8s.pingk8s.overviewk8s.resource_usagek8s.eventsk8s.events_timelinek8s.hpa_debugk8s.vpa_debugk8s.best_practicek8s.listk8s.describek8s.graph
Trigger Conditions
Activate for requests like:
- cluster health check
- resource hotspots
- scaling seems wrong
- noisy warnings across namespace
- capacity planning ahead of release
- post-incident verification
Baseline Diagnostic Sequence
- verify active context with
k8s.context - verify control plane with
k8s.ping - collect baseline with
k8s.overview - detect pressure with
k8s.resource_usage - correlate warnings with
k8s.events_timeline - inspect autoscaling using
k8s.hpa_debugandk8s.vpa_debug - score workload configuration with
k8s.best_practice - produce prioritized recommendations
Parameter Examples
k8s.context current:
{
"action": "current"
}
k8s.context list:
{
"action": "list"
}
k8s.ping:
{}
k8s.overview namespace:
{
"namespace": "payments"
}
k8s.resource_usage cpu hotspot view:
{
"namespace": "payments",
"includePods": true,
"includeNodes": true,
"sortBy": "cpu",
"limit": 40
}
k8s.resource_usage memory hotspot view:
{
"namespace": "payments",
"includePods": true,
"includeNodes": true,
"sortBy": "memory",
"limit": 40
}
k8s.events namespace warnings and normals:
{
"namespace": "payments"
}
k8s.events_timeline warning-only:
{
"namespace": "payments",
"includeNormal": false,
"limit": 150
}
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 · 492 lines · 0 tokens per session scan A f3ab272a3ecb
k8s-diagnostics 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,518 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
bazel-k8s-expert
Expert knowledge for deploying Quarkus/Java applications to Kubernetes using Bazel. Covers rulesk8s, Helm, Kustomize, ConfigMaps, Secrets, and health probes.
kubernetes-operator
Deploy and manage applications on Kubernetes. Covers deployments, services, ingress, HPA, secrets, and production-grade cluster configuration.
upgrade-cluster
Use when upgrading or hardening an existing kube-hetzner cluster, including module version bumps, provider lockfile refreshes, k3s/RKE2 channel/version upgrades, immutable node replacement, system-upgrade-controller changes, or live cluster rollout validation.
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.