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 CoWork-OS/CoWork-OS --skill kubernetes-opsgit clone --depth 1 https://github.com/CoWork-OS/CoWork-OSWrote 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/cowork-os/cowork-os/kubernetes-ops)<a href="https://agentmods.dev/skills/cowork-os/cowork-os/kubernetes-ops"><img src="https://agentmods.dev/badge/skills/cowork-os/cowork-os/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/cowork-os/cowork-os/kubernetes-ops"><img src="https://agentmods.dev/badge/skills/cowork-os/cowork-os/kubernetes-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.00396 |
| Opus 5 | $0.00015 | $0.00198 |
| Sonnet 5 | $0.00006 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00040 |
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 Operations
Purpose
Kubernetes cluster operations: kubectl commands, manifest generation, Helm charts, RBAC, debugging, and deployment strategies.
Routing
- Use when: Use when the user asks about Kubernetes, k8s, kubectl, pods, deployments, services, ingress, Helm charts, RBAC, container orchestration, or cluster management.
- Do not use when: Do not use for Docker Compose (use docker-compose-ops), Terraform IaC (use terraform-ops), or general cloud migration (use cloud-migration).
- Outputs: kubectl commands, Kubernetes manifests (YAML), Helm operations, and debugging guidance.
- Success criteria: Returns valid Kubernetes manifests or kubectl commands that can be applied to a cluster.
Trigger Examples
Positive
- Use the kubernetes-ops skill for this request.
- Help me with kubernetes operations.
- Use when the user asks about Kubernetes, k8s, kubectl, pods, deployments, services, ingress, Helm charts, RBAC, container orchestration, or cluster management.
- Kubernetes Operations: provide an actionable result.
Negative
- Do not use for Docker Compose (use docker-compose-ops), Terraform IaC (use terraform-ops), or general cloud migration (use cloud-migration).
- Do not use kubernetes-ops for unrelated requests.
- This request is outside kubernetes operations scope.
- This is conceptual discussion only; no tool workflow is needed.
Runtime Prompt
- Current runtime prompt length: 898 characters.
- Runtime prompt is defined directly in
../kubernetes-ops.json.
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 · 42 lines · 29 tokens per session scan A 485fded7f2cb
kubernetes-ops is a skill published in the GitHub repository CoWork-OS/CoWork-OS (452 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 396 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-09-03.
Other skills, from other repositories
nvcf-self-managed-prerequisite
Install the prerequisites the NVCA operator / compute plane needs before nvcf-nvca-install can succeed: the operator tool nvcf-cli (required by the compute-plane stack's register-cluster step), KAI Scheduler (for the KAIScheduler feature gate), and the SMB CSI driver (for the sharedStorage Samba sidecar PVCs). The two…
portal-relay
Set up and run a public Portal relay on any Linux host with a public IP — Docker Compose deployment, embedded authoritative DNS with one-time NS delegation, optional TCP/UDP lease ports for game hosting, and registration in the public relay pool. Use when the user asks to run their own relay, contribute a relay to the…
olares-chart
Olares app packaging and chart authoring via olares-cli chart — port a repo, docker-compose, or generic Helm chart; build/push the image; author, lint, package, and deploy an OlaresManifest; wire storage, middleware, entrances, env, and GPU; edit the chart after diagnosis. Runtime failure diagnosis is olares-doctor…
olares-cluster
Olares ControlHub K8s runtime view via olares-cli cluster — inspect pods, containers, workloads, logs, jobs, cronjobs, namespaces, nodes, and middleware; exec, scale, restart, or delete K8s objects. Use for raw runtime objects and logs, not app lifecycle (market), resource metrics (dashboard), or host install.
node-deploy
Build and deploy Node.js applications — version detection, package managers, framework-specific builds, monorepo support, and Dockerfile patterns. Use when deploying a Node.js, JavaScript, or TypeScript project, or when package.json is detected in the repository.
container-resource-tuning
Size container memory and CPU limits, diagnose OOM kills and CPU throttling, and recommend resource adjustments by ecosystem. Use when containers are being OOM-killed, running slowly, or when setting initial resource limits for a deployment.