Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/kurtosis-tech/kurtosisnpx agentmods add skills/kurtosis-tech/kurtosis/k8s-dev-deployWrote 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-dev-deploy)<a href="https://agentmods.dev/skills/kurtosis-tech/kurtosis/k8s-dev-deploy"><img src="https://agentmods.dev/badge/skills/kurtosis-tech/kurtosis/k8s-dev-deploy.svg" alt="Measured on agentmods" 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.00078 | $0.01276 |
| Opus 5 | $0.00039 | $0.00638 |
| Sonnet 5 | $0.00016 | $0.00255 |
| Haiku 4.5 | $0.00008 | $0.00128 |
Grade A, and why
k8s-dev-deploy 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 8d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
K8s Dev Deploy
Build and deploy Kurtosis from source to a Kubernetes cluster for testing without making a release.
Overview
Three container images must be built and pushed:
engine— fromengine/server/Dockerfilecore(APIC) — fromcore/server/Dockerfilefiles-artifacts-expander— fromcore/files_artifacts_expander/Dockerfile
The CLI binary is also rebuilt locally.
All images share the same tag, which is set in kurtosis_version/kurtosis_version.go as KurtosisVersion. This version is compiled into the engine binary and used at runtime to pull the core and files-artifacts-expander images.
Steps
1. Determine Docker Hub username and generate a unique tag
DOCKER_USER=$(docker info 2>/dev/null | grep Username | awk '{print $2}')
TAG="$(git rev-parse --short HEAD)-$(date +%s)"
2. Update image references to use the user's Docker Hub
Edit these three constants to replace kurtosistech with $DOCKER_USER:
| File | Constant | Default Value |
|---|---|---|
engine/launcher/engine_server_launcher/engine_server_launcher.go |
containerImage |
kurtosistech/engine |
core/launcher/api_container_launcher/api_container_launcher.go |
containerImage |
kurtosistech/core |
core/server/api_container/server/startosis_engine/kurtosis_types/service_config/service_config.go |
filesArtifactsExpanderImage |
kurtosistech/files-artifacts-expander |
3. Set the version tag
Edit kurtosis_version/kurtosis_version.go and set KurtosisVersion to the generated $TAG.
IMPORTANT: Always use a unique tag (include a timestamp) to avoid Kubernetes node image caching issues. Nodes with imagePullPolicy: IfNotPresent won't re-pull an image with the same tag.
4. Build all binaries (parallel)
# Engine
CGO_ENABLED=0 GOOS=linux GOARCH=arm64 go build -o engine/server/build/kurtosis-engine.arm64 engine/server/engine/main.go
CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -o engine/server/build/kurtosis-engine.amd64 engine/server/engine/main.go
# Core (APIC)
CGO_ENABLED=0 GOOS=linux GOARCH=arm64 go build -o core/server/build/api-container.arm64 core/server/api_container/main.go
CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -o core/server/build/api-container.amd64 core/server/api_container/main.go
# Files Artifacts Expander
CGO_ENABLED=0 GOOS=linux GOARCH=arm64 go build -o core/files_artifacts_expander/build/files-artifacts-expander.arm64 core/files_artifacts_expander/main.go
CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -o core/files_artifacts_expander/build/files-artifacts-expander.amd64 core/files_artifacts_expander/main.go
# CLI (local use)
go build -o /tmp/kurtosis ./cli/cli/
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.
- 8d ago First seen · 108 lines · 78 tokens per session scan A 085241d862c8
k8s-dev-deploy is a skill published in the GitHub repository kurtosis-tech/kurtosis (550 stars, last pushed 5d ago), licensed Apache-2.0. It adds 78 tokens to every session and 1,276 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-30.
Other skills, from other repositories
synapse
Use when the user needs to inspect or manage Synapse-managed Docker/Compose infrastructure via flux, or SSH/local host files, processes, logs, ZFS, and allowlisted commands via scout. Prefer MCP tools first, CLI second, REST last; use write or confirmation-gated actions only when explicitly requested or necessary.
xcloud-docker-deploy
Skill "xcloud-docker-deploy" from Asif2BD/xCloud-Docker-Deploy-Skill, covering xcloud docker deploy v1.4.1, start here, how xcloud works, current xcloud api + agent skills context and api token flow.
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"…
ecspresso
ECS deployment tool - deploy, manage, and troubleshoot ECS services.
infra-conventions
Infrastructure and deployment conventions. Auto-injected into devops-aware agents - not user-invocable.
isrvd-ops
Operations instructions for using the isrvd API to deploy containers, manage services and images, configure routes, handle files, and use a web terminal. The instructions include Python, Node.js, and Bash helper scripts.