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/docker-local-buildWrote 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/docker-local-build)<a href="https://agentmods.dev/skills/kurtosis-tech/kurtosis/docker-local-build"><img src="https://agentmods.dev/badge/skills/kurtosis-tech/kurtosis/docker-local-build/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/docker-local-build"><img src="https://agentmods.dev/badge/skills/kurtosis-tech/kurtosis/docker-local-build.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 106 Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
- high Tool Misuse · line 107 Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
- high Tool Misuse · line 108 Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
- high Tool Misuse · line 109 Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
- high Tool Misuse · line 110 Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
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.00056 | $0.01430 |
| Opus 5 | $0.00028 | $0.00715 |
| Sonnet 5 | $0.00011 | $0.00286 |
| Haiku 4.5 | $0.00006 | $0.00143 |
Grade A, and why
docker-local-build 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 10d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Local Build
Build all Kurtosis components from source and test them locally on Docker.
Overview
This skill builds the full Kurtosis stack for local Docker testing:
- Engine — Docker image
kurtosistech/engine - Core (APIC) — Docker image
kurtosistech/core - Files Artifacts Expander — Docker image
kurtosistech/files-artifacts-expander - CLI — binary at
.tmp/kurtosis, installed to/usr/local/bin/kurtosis
All images are tagged with the current git short SHA (+ -dirty if uncommitted changes exist) via scripts/get-docker-tag.sh. The same tag is compiled into the CLI as KurtosisVersion.
Quick build (recommended)
Run the wrapper script from the repo root. It handles version generation, image builds, CLI compilation, installation, and engine reset:
./scripts/local-build.sh
Environment variables
| Variable | Default | Description |
|---|---|---|
INSTALL_PATH |
/usr/local/bin/kurtosis |
Where to install the CLI binary |
BUILD_IMAGES |
true |
Set to false to skip Docker image builds (CLI only) |
DEBUG_IMAGE |
false |
Build debug images with delve debugger |
PODMAN_MODE |
false |
Use podman instead of docker |
RESET_KURTOSIS_AFTER_BUILD |
true |
Stop engine and clean containers after build |
Examples
# Full build + install + reset
./scripts/local-build.sh
# CLI only (skip image builds)
BUILD_IMAGES=false ./scripts/local-build.sh
# Build with debug images
DEBUG_IMAGE=true ./scripts/local-build.sh
# Install to a custom path
INSTALL_PATH=/tmp/kurtosis ./scripts/local-build.sh
# Skip engine reset (keep running enclaves)
RESET_KURTOSIS_AFTER_BUILD=false ./scripts/local-build.sh
Manual build (step by step)
1. Generate version constants
./scripts/generate-kurtosis-version.sh
This writes the git-based version tag into kurtosis_version/kurtosis_version.go.
2. Build Docker images
The existing build scripts handle binary compilation, unit tests, and Docker image building:
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.
- 10d ago First seen · 152 lines · 56 tokens per session scan A cd27c691f69b
docker-local-build is a skill published in the GitHub repository kurtosis-tech/kurtosis (551 stars, last pushed today), licensed Apache-2.0. It adds 56 tokens to every session and 1,430 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.