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 arjunprabhulal/devops-skills --skill kubernetes-storagegit clone --depth 1 https://github.com/arjunprabhulal/devops-skillsWrote 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/arjunprabhulal/devops-skills/kubernetes-storage)<a href="https://agentmods.dev/skills/arjunprabhulal/devops-skills/kubernetes-storage"><img src="https://agentmods.dev/badge/skills/arjunprabhulal/devops-skills/kubernetes-storage/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/arjunprabhulal/devops-skills/kubernetes-storage"><img src="https://agentmods.dev/badge/skills/arjunprabhulal/devops-skills/kubernetes-storage.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.00098 | $0.01476 |
| Opus 5.5 | $0.00039 | $0.00590 |
| Sonnet 5.5 | $0.00020 | $0.00295 |
| Haiku 4.5 | $0.00010 | $0.00148 |
Grade A, and why
kubernetes-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 1mo 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kubernetes Storage
Kubernetes was designed for stateless, disposable pods, and storage is the layer where that assumption breaks down and has to be bolted back on carefully. A pod can be rescheduled to any node at any time; the volume it depends on has to either follow it there or already be reachable from there — get this wrong and a routine reschedule becomes a data-loss incident.
Treat every PVC as a promise about what happens when the pod above it dies, not just where the bytes live today. The reclaim policy and access mode you pick now decide what happens the day something goes wrong, not the day it's created.
1. Understand the claim as a request, not a guarantee
A PVC asks for a certain size, access mode, and StorageClass; the PV that satisfies it is either
pre-provisioned or, more commonly now, dynamically created by the StorageClass's provisioner. A
Pending PVC almost always means no StorageClass/provisioner can satisfy what was asked for —
capacity, access mode, or a zone constraint that doesn't match available storage.
kubectl get pvc <name> # Pending? check events
kubectl describe pvc <name> # provisioning failure reason
kubectl get storageclass # is the referenced class real, and is one default?
- No default StorageClass and no
storageClassNamespecified means the PVC has nothing to bind to — this is a common first-cluster surprise. - Zonal mismatch: many cloud provisioners create volumes in a specific zone; if the pod gets scheduled to a different zone, attachment fails even though the PV exists.
Done when: every PVC is Bound, or the Pending reason is identified from describe, not
guessed.
2. Match access mode to what the workload actually does
ReadWriteOnce (single node), ReadWriteMany (multiple nodes, needs a filesystem-based backend
like NFS/EFS/Filestore), and ReadOnlyMany are not interchangeable, and picking RWX by default
"just in case" often forces a slower, more expensive storage backend than the workload needs.
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.
- 1mo ago First seen · 113 lines · 98 tokens per session scan A 20fcfe3d3186
kubernetes-storage is a skill published in the GitHub repository arjunprabhulal/devops-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 98 tokens to every session and 1,476 once invoked, about $0.0004 per session on Opus 5.5. 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-31.
Other skills, from other repositories
bigquery-udfs
Creates, deploys, and troubleshoots BigQuery User-Defined Functions (UDFs) and Remote Functions across SQL, JavaScript, Python, and Cloud Run endpoints. Use when writing custom scalar or aggregate functions in BigQuery, installing PyPI packages or Cloud Storage libraries in a Python or JavaScript UDF, or calling…
dbt-sf-to-bq-translator
Translates Snowflake dbt SQL models to Standardized BigQuery SQL. Handles SQL compilation, Jinja macro placeholder masking, BigQuery Translation Service migration workflows, AST-based config transformations, explicit type casting, JSON extraction standardization, and deduplication. Use when migrating Snowflake dbt…
bigquery-observability
Provides data-retrieval best practices, tool selection guidance, and performant SQL query syntax for BigQuery telemetry across INFORMATIONSCHEMA, Cloud Monitoring, and the REST API. Use when the telemetry to fetch is already known, selecting telemetry tools, writing performant INFORMATIONSCHEMA queries, retrieving…
bigquery-migration-sql-translator
Translates SQL queries, DDL schemas, and stored procedures from legacy database dialects (Teradata, Oracle, Redshift, Snowflake, SparkSQL, HiveQL) to BigQuery GoogleSQL using the BigQuery Migration Service (BQMS) MCP server. Use when translating legacy SQL queries, migrating schemas or metadata zip archives, or…
bigquery-optimization
Provides workflows to optimize BigQuery environments (capacity planning, editions), storage assets (partitioning, clustering, storage lifecycles, billing models), and SQL queries. Use when optimizing cost, modeling Edition migrations, rightsizing reservations, evaluating logical vs. physical storage, designing table…
alloydb-basics
Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB Model Context Protocol (MCP) tools for automated database operations. Use when creating, configuring, or administering AlloyDB databases. Do NOT use for general PostgreSQL instances (e.g. Cloud SQL) or other GCP databases.