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 Goodsmileduck/claude-registry --skill kubernetes-operatorsgit clone --depth 1 https://github.com/Goodsmileduck/claude-registryWrote 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/goodsmileduck/claude-registry/kubernetes-operators)<a href="https://agentmods.dev/skills/goodsmileduck/claude-registry/kubernetes-operators"><img src="https://agentmods.dev/badge/skills/goodsmileduck/claude-registry/kubernetes-operators/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/goodsmileduck/claude-registry/kubernetes-operators"><img src="https://agentmods.dev/badge/skills/goodsmileduck/claude-registry/kubernetes-operators.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.00076 | $0.01977 |
| Opus 5 | $0.00038 | $0.00988 |
| Sonnet 5 | $0.00015 | $0.00395 |
| Haiku 4.5 | $0.00008 | $0.00198 |
Grade A, and why
kubernetes-operators 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kubernetes Operators — CRD and reconcile review
For pod-level debugging (CrashLoopBackOff, ImagePullBackOff, scheduling failures) see the kubernetes-operations skill. For Argo-managed deployments see argocd-operations.
Most "operator bugs" are reconcile-loop bugs, not Kubernetes bugs: missing finalizers, blocking calls, no requeue on transient error, status drift, RBAC over-grant. The three Python scripts shipped here catch the deterministic subset before code reaches a cluster.
When to invoke
Run the analyzers first — they're stdlib Python, fast, and surface most routine issues:
SKILL=plugins/kubernetes-skills/skills/kubernetes-operators
python3 "$SKILL/scripts/crd_validator.py" --crd config/crd/
python3 "$SKILL/scripts/reconcile_lint.py" --controller controllers/
python3 "$SKILL/scripts/operator_capability_audit.py" --operator-dir .
All three accept --format json. Triage by severity: FAIL blocks merge, WARN files an issue.
Pre-flight: is an operator the right shape?
Operators are for stateful, lifecycle-managed workloads. Reach for one when:
- The thing being managed has an external API (RDS, Kafka topics, GitHub repos).
- Day-2 operations are non-trivial (backup, restore, version upgrade, failover).
- A Helm chart + bash isn't enough — you need a controller that observes and re-acts.
Don't reach for an operator when:
| Want | Better tool |
|---|---|
| Run a workload | Deployment / StatefulSet / Job |
| Package + parameterize manifests | Helm chart or Kustomize |
| Sync repo → cluster | ArgoCD / Flux |
| External-resource lifecycle, no day-2 complexity | Terraform / Crossplane composition |
Core principle: reconcile is declarative, not imperative
The wrong shape:
if creating: do A
elif updating: do B
elif deleting: do C
The right shape:
desired = read(spec)
actual = observe(world)
diff = compare(desired, actual)
for change in diff: apply(change) # idempotently
update_status()
What ships with it
5 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 · 157 lines · 76 tokens per session scan A c1b16eff9ebf
kubernetes-operators is a skill published in the GitHub repository Goodsmileduck/claude-registry (1 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 1,977 once invoked, about $0.0004 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
devops-best-practices
Opinionated production-grade DevOps defaults for Terraform, Kubernetes, CI/CD, Docker, cloud security, observability, cost, and disaster recovery. ALWAYS use when generating, reviewing, or modifying any infrastructure code, Kubernetes manifests (Deployment, Service, StatefulSet, Helm, Kustomize), Terraform (.tf…
cloudflare-temporary-deploy
Deploy a Worker live, no account, via wrangler --temporary.
tensorrt-llm
High-throughput LLM inference on NVIDIA GPUs.
stripe-projects
Provision SaaS services + sync creds via Stripe Projects.
cloud-sync
Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.
cli-backup-sync
Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.