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 kurtosis-tech/kurtosis --skill k8s-clean-clustergit clone --depth 1 https://github.com/kurtosis-tech/kurtosisWrote 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/kurtosis-tech/kurtosis/k8s-clean-cluster)<a href="https://agentmods.dev/skills/kurtosis-tech/kurtosis/k8s-clean-cluster"><img src="https://agentmods.dev/badge/skills/kurtosis-tech/kurtosis/k8s-clean-cluster/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/kurtosis-tech/kurtosis/k8s-clean-cluster"><img src="https://agentmods.dev/badge/skills/kurtosis-tech/kurtosis/k8s-clean-cluster.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.00059 | $0.00739 |
| Opus 5 | $0.00030 | $0.00369 |
| Sonnet 5 | $0.00012 | $0.00148 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
k8s-clean-cluster 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
K8s Clean Cluster
Force-clean all Kurtosis resources from a Kubernetes cluster when the normal kurtosis clean -a command hangs or fails.
When to use
kurtosis clean -ahangs for more than a few minutes- Orphaned kurtosis namespaces remain after a failed clean
remove-dir-pod-*pods are stuck in Pending state- Engine start fails because old resources exist
Steps
1. Kill any running kurtosis processes
pkill -f "kurtosis gateway" 2>/dev/null
pkill -f "kurtosis clean" 2>/dev/null
2. Stop the engine gracefully (if possible)
kurtosis engine stop || true
3. Delete all kurtosis namespaces
# List them first
kubectl get ns | grep kurtosis
# Delete all kurtosis namespaces (engine, enclaves, logs)
kubectl get ns | grep kurtosis | awk '{print $1}' | xargs -r kubectl delete ns --force --grace-period=0
4. Clean up cluster-scoped resources
# Delete kurtosis cluster roles
kubectl get clusterrole | grep kurtosis | awk '{print $1}' | xargs -r kubectl delete clusterrole
# Delete kurtosis cluster role bindings
kubectl get clusterrolebinding | grep kurtosis | awk '{print $1}' | xargs -r kubectl delete clusterrolebinding
5. Clean up stuck pods
# Force-delete any remaining kurtosis pods
kubectl get pods -A | grep kurtosis | awk '{print $2 " -n " $1}' | xargs -L1 kubectl delete pod --force --grace-period=0
# Clean up evicted pods
kubectl get pods -A | grep Evicted | awk '{print $2 " -n " $1}' | xargs -L1 kubectl delete pod --force --grace-period=0
6. Verify clean state
kubectl get ns | grep kurtosis
kubectl get pods -A | grep kurtosis
kubectl get ds -A | grep kurtosis
All three commands should return empty results.
7. Restart
kurtosis engine start
kurtosis gateway &
Why clean hangs
The most common cause is the fluentbit logs collector Clean method which:
- Evicts all DaemonSet pods by adding a non-existent node selector
- Waits for each pod to terminate (up to 5 min per pod, sequentially)
- Creates
remove-dir-podcleanup pods targeted at each node - Cleanup pods on tainted/unhealthy nodes get stuck in Pending
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.
- 11d ago First seen · 92 lines · 59 tokens per session scan A 2efe2dbe5b0c
k8s-clean-cluster is a skill published in the GitHub repository kurtosis-tech/kurtosis (551 stars, last pushed 2d ago), licensed Apache-2.0. It adds 59 tokens to every session and 739 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-30.
Other skills, from other repositories
harbor
CLI toolkit for managing containerized LLM services. Use when the user wants to start, stop, configure, or manage AI/LLM services like Ollama, Open WebUI, llama.cpp, vLLM, LiteLLM, ComfyUI, and 250+ others. Triggers on requests to "run a model", "start ollama", "set up an LLM", "configure harbor", "manage services"…
branchbox-devcontainer-guardrails
Use when modifying BranchBox devcontainer/bootstrap workflows, compose templates, feature env-stash behavior, or manual E2E harness/release docs. Apply issue.
l337-docker
Drive Docker through the docker CLI - containers, images, networks, volumes, Compose, Swarm services/stacks/nodes/secrets, buildx, Scout, OCI registries, plugins, contexts and remote daemons. Covers inspection, deployment, debugging, security auditing, build/publish and cleanup, with bounded output and a confirmation…
ilo
Run builds, tests, and other tooling inside a reproducible, containerized dev environment via the ilo CLI instead of on the host. Use this whenever a project relies on ilo, devcontainers, or container-based build environments — it has a .ilo.rc / .ilo/ilo.rc, dev/ argument files, a Containerfile/Dockerfile, a…
dev-environment-setup
Use this skill as a router/index when the user faces a development environment question that spans multiple domains: containers (Docker/Podman), WSL2 on Windows, office-skill dependencies (DOCX/PDF/XLSX/ PPTX), or system tools (LibreOffice/Poppler/Pandoc/Tesseract). For pure Python issues use python-runtime skill; for…
docker-containerization
Containerize applications with multi-stage Dockerfiles, Docker Compose orchestration, image optimization, and container security. Covers Python, Node.js, and multi-service architectures. Triggers on Docker, containerization, or container orchestration requests.