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-storagenpx skills add yindia/rootcause --skill k8s-storagegit 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-storage)<a href="https://agentmods.dev/skills/yindia/rootcause/k8s-storage"><img src="https://agentmods.dev/badge/skills/yindia/rootcause/k8s-storage.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.01980 |
| Opus 5 | $0.00000 | $0.00990 |
| Sonnet 5 | $0.00000 | $0.00396 |
| Haiku 4.5 | $0.00000 | $0.00198 |
Grade A, and why
k8s-storage 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 5d 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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: k8s-storage
Comprehensive Kubernetes persistent storage diagnostics covering PVC lifecycle, StorageClass behavior, snapshot workflows, mount failures, and attach/detach errors.
Scope
Use this skill for stateful workload issues where data volume behavior blocks scheduling, startup, recovery, scaling, or deletion.
Trigger Phrases
Use this skill when the user mentions:
- pvc pending
- pv not bound
- volume mount failed
- multi attach error
- volumeattachment issue
- storage class misconfiguration
- csi error
- ebs or efs issue
- snapshot restore failed
- pod stuck containercreating
- filesystem readonly
- disk full in statefulset
RootCause Tools Allowed
Only use these tool names in this skill:
k8s.storage_debugk8s.describek8s.listk8s.eventsk8s.events_timeline
PVC Lifecycle Reference
Typical lifecycle states
| PVC Phase | Meaning | Typical Next Step |
|---|---|---|
Pending |
Not yet bound to a volume | Inspect StorageClass and provisioning events |
Bound |
Successfully attached to PV | Validate pod mount and filesystem |
Lost |
Underlying PV unavailable/reclaimed unexpectedly | Trace reclaim events and backend health |
PV lifecycle states commonly observed
| PV Phase | Meaning | Operator Concern |
|---|---|---|
Available |
Unclaimed static volume | Match claim requirements |
Bound |
Claimed by PVC | Confirm claimRef is expected |
Released |
PVC removed, reclaim pending | Reclaim policy and cleanup process |
Failed |
Provisioning/reclaim failed | Storage backend or driver issue |
StorageClass Configuration Checklist
When diagnosing provisioning behavior, verify:
provisionervalue maps to installed CSI driver.volumeBindingModeis expected (ImmediateorWaitForFirstConsumer).reclaimPolicyaligns with retention policy (DeleteorRetain).allowVolumeExpansionmatches growth requirements.- parameters match cloud-specific constraints.
Use k8s.describe on StorageClass for all checks.
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.
- 5d ago First seen · 308 lines · 0 tokens per session scan A 78d07b196ae6
k8s-storage 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,980 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-review
Kubernetes & Cloud-Native Review: Reviews Kubernetes manifests, Helm charts, and cloud-native configurations for security, reliability, resource management, and best practices. Covers pods, deployments, services, ingress, RBAC, network policies, HPA, PDB, security contexts, and GitOps patterns. Use when the user…
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.
securing-helm-chart-deployments
Secure Helm chart deployments by validating chart integrity, scanning templates for misconfigurations, and enforcing security contexts in Kubernetes releases.
dependabot-batch
Use when reviewing Radar's weekly Dependabot PRs and replacing the safe, 72-hour-soaked updates with one changelog-vetted, tested PR.