k8s-workflow

k8s-workflow is a skill for Claude Code from Sagart-cactus/claude-k8s-plugin. It costs 18 tokens per session (859 once invoked), scanned A, original, MIT.

A development workflow for building Kubernetes operators, which are programs that manage custom resources in Kubernetes clusters.

In plain words
What is it for?
Designing custom resources, generating controller and webhook code, setting up development files, installing them in kind, and testing their behavior.
Why use it?
It keeps development limited to local kind clusters, adds safety checks, and provides a repeatable build and validation loop.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the k8s plugin — 4 skills, 7 commands, 2 hooks shipped together

Good fit Designing custom resources, generating controller and webhook code, setting up development files, installing them in kind, and testing their behavior.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sagart-cactus/claude-k8s-plugin/k8s-operator-workflow
Install

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.

Any agent
npx skills add Sagart-cactus/claude-k8s-plugin --skill k8s-operator-workflow
Clone the repo
git clone --depth 1 https://github.com/Sagart-cactus/claude-k8s-plugin

Made for: Claude Code.

Or install k8s, the plugin that ships this one along with the rest of its 4 skills, 7 commands, 2 hooks.

Wrote 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.

agentmods badge for k8s-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/sagart-cactus/claude-k8s-plugin/k8s-operator-workflow/github.svg)](https://agentmods.dev/skills/sagart-cactus/claude-k8s-plugin/k8s-operator-workflow)
Your own site
<a href="https://agentmods.dev/skills/sagart-cactus/claude-k8s-plugin/k8s-operator-workflow"><img src="https://agentmods.dev/badge/skills/sagart-cactus/claude-k8s-plugin/k8s-operator-workflow/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.

agentmods 80×15 button for k8s-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/sagart-cactus/claude-k8s-plugin/k8s-operator-workflow"><img src="https://agentmods.dev/badge/skills/sagart-cactus/claude-k8s-plugin/k8s-operator-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 859 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00018 $0.00859
Opus 5 $0.00009 $0.00430
Sonnet 5 $0.00004 $0.00172
Haiku 4.5 $0.00002 $0.00086

Measured 11d ago against content hash b8ca6813e269, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

k8s-workflow 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 11d 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.

skills/k8s-operator-workflow/SKILL.md · 96 lines

How it starts

The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Kubernetes Operator Workflow

Operating Mode

  • Dev-only: Target kind clusters only. Refuse operations on non-kind contexts unless user explicitly overrides.
  • MCP preferred: If a Kubernetes MCP server is available, use it for cluster validation. Otherwise, fall back to kubectl commands.
  • Safety first: Allow only kind-* contexts. Avoid destructive operations by default.

Agent Responsibilities

  1. Ask questions to clarify CRD purpose, fields, validation rules, webhook type, and safety constraints.
  2. Generate CRD schema and example custom resources.
  3. Scaffold controller and webhook code using Go + Kubebuilder patterns.
  4. Create dev loop config: Tiltfile + Kustomize dev overlay + Makefile target.
  5. Create a kind cluster and install CRDs/webhooks.
  6. Validate behavior using MCP or kubectl and logs.
  7. Iterate until requirements are satisfied.

Required Q&A (ask before writing code)

Always ask these 10 questions and wait for answers:

  1. CRD purpose (1 sentence)
  2. Spec fields (name + type + required?)
  3. Status fields (what should be reported?)
  4. Webhook type (validating, mutating, or both)
  5. Defaulting rules (if any)
  6. Validation rules (invariants)
  7. RBAC scope (namespace or cluster)
  8. Resource ownership (what objects are created/managed)
  9. Failure policy (for webhooks)
  10. Safety gates (annotations/labels to enable mutations)

Dev Fast Loop Workflow

Default to Tilt (tilt up or make dev) for all build and deploy cycles. Do not manually run docker build, kind load, or kustomize build | kubectl apply unless Tilt live-update cannot handle the change.

Overview

  • One command: make dev (wraps tilt up)
  • Tilt builds the Docker image, loads it into kind, and applies Kustomize manifests
  • Local go build produces the manager binary
  • Tilt live-update syncs the binary into the running manager pod
  • Tilt kills the process to restart with new code

Iteration Cycle

  1. Edit Go files (types, controller, webhook)
  2. Tilt recompiles locally
  3. Binary syncs into the running pod
  4. Process restarts
  5. Check logs/events for feedback

Read the full file on GitHub · 96 lines

Changes

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.

  1. 11d ago First seen · 96 lines · 18 tokens per session scan A b8ca6813e269

Subscribe to this mod's changes

k8s-workflow is a skill published in the GitHub repository Sagart-cactus/claude-k8s-plugin (34 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 859 once invoked, about $0.0001 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-30.

Related

Other skills, from other repositories

deploy-docker-compose

Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…

omnigent-ai/omnigent · 84 tokens

compute-env-setup

Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.

companion-inc/feynman · 45 tokens

securing-kubernetes-on-cloud

This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…

xalgorix/xalgorix · 80 tokens

detecting-privilege-escalation-in-kubernetes-pods

Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.

xalgorix/xalgorix · 40 tokens

implementing-rbac-hardening-for-kubernetes

Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.

xalgorix/xalgorix · 41 tokens

docker-socket-mount

Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.

PurpleAILAB/Decepticon · 67 tokens