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 FutureJJ/claude-skills --skill kubernetes-opsgit clone --depth 1 https://github.com/FutureJJ/claude-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/futurejj/claude-skills/kubernetes-ops)<a href="https://agentmods.dev/skills/futurejj/claude-skills/kubernetes-ops"><img src="https://agentmods.dev/badge/skills/futurejj/claude-skills/kubernetes-ops/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/futurejj/claude-skills/kubernetes-ops"><img src="https://agentmods.dev/badge/skills/futurejj/claude-skills/kubernetes-ops.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.00052 | $0.00368 |
| Opus 5 | $0.00026 | $0.00184 |
| Sonnet 5 | $0.00010 | $0.00074 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
kubernetes-ops 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.
What it actually says
Kubernetes Ops
You are a Kubernetes expert focused on production operations and debugging.
Core Principles
- Declarative over imperative. Use YAML manifests, not
kubectl run. - Resource limits always. Every container needs CPU/memory requests AND limits.
- Health checks mandatory. Liveness probe prevents stuck containers. Readiness probe prevents traffic to unready pods.
- RBAC least privilege. ServiceAccounts with minimal permissions per workload.
Debugging Checklist
kubectl get pods— check STATUS (CrashLoopBackOff, ImagePullBackOff, Pending)kubectl describe pod <name>— check Events section for scheduling/pull errorskubectl logs <pod> --previous— check logs from crashed containerkubectl exec -it <pod> -- sh— interactive debugging
Anti-Patterns
- No resource limits — one pod can starve the entire node
- Using
latesttag — no rollback possible, non-deterministic - Storing secrets in ConfigMaps — use Secrets (or external secrets manager)
- Single replica for production services — no high availability
Reference Guide
| Topic | Reference | Load When |
|---|---|---|
| Workload patterns | references/workloads.md |
Deployments, StatefulSets, Jobs, HPA |
| Networking & security | references/networking.md |
Services, Ingress, NetworkPolicies, RBAC |
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 · 36 lines · 52 tokens per session scan A d400d3c47f91
kubernetes-ops is a skill published in the GitHub repository FutureJJ/claude-skills (3 stars, last pushed 6mo ago), licensed MIT. It adds 52 tokens to every session and 368 once invoked, about $0.0003 per session on Opus 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
offensive-container-escape
Container escape and breakout techniques targeting Docker, containerd, and Podman runtimes. Covers privileged container breakout via host filesystem mount and nsenter, Docker socket abuse through /var/run/docker.sock, Linux capability exploitation including CAPSYSADMIN, CAPSYSPTRACE, and CAPNETADMIN, cgroup v1…
container-orchestration
Docker, Kubernetes, and AWS ECS/Fargate patterns. Triggers on: Dockerfile, docker-compose, kubernetes, k8s, helm, pod, deployment, service, ingress, container, image, ecs, fargate, task definition, ecs service, awsvpc, FARGATESPOT, ALB, ecs vs kubernetes.
deploy-ninja
Handles zero-downtime deployments: blue-green, canary releases, rolling updates, and feature flag rollouts. Covers Kubernetes, Docker, Cloudflare Workers, Terraform, and CI/CD pipeline setup. Use this skill when the user wants to deploy an application, set up a deployment pipeline, implement canary releases, configure…
infra-automation
Manages infrastructure operations: DNS records, SSL certificates, Cloudflare Workers, CDN configuration, and domain provisioning. Use this skill whenever the user mentions Cloudflare, DNS, SSL, Workers, domain setup, CDN config, TLS hardening, zone management, or any infrastructure automation task — even if they just…
kubernetes-specialist
Use when deploying or managing Kubernetes workloads. Invoke to create deployment manifests, configure pod security policies, set up service accounts, define network isolation rules, debug pod crashes, analyze resource limits, inspect container logs, or right-size workloads. Use for Helm charts, RBAC policies…
ecs
AWS ECS container orchestration for running Docker containers. Use when deploying containerized applications, configuring task definitions, setting up services, managing clusters, or troubleshooting container issues.