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 agentmods add skills/kurtosis-tech/kurtosis/docker-debugnpx skills add kurtosis-tech/kurtosis --skill docker-debuggit 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/docker-debug)<a href="https://agentmods.dev/skills/kurtosis-tech/kurtosis/docker-debug"><img src="https://agentmods.dev/badge/skills/kurtosis-tech/kurtosis/docker-debug.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00045 | $0.00989 |
| Opus 5 | $0.00023 | $0.00495 |
| Sonnet 5 | $0.00009 | $0.00198 |
| Haiku 4.5 | $0.00005 | $0.00099 |
Grade A, and why
docker-debug scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
kurtosis service exec <enclave-name> <service-name> -- wget -qO- http://<other-service>:<port>/endpoint How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Debug
Diagnose and fix issues with Kurtosis running on a local Docker engine.
Quick triage
# Check engine is running
kurtosis engine status
# List all kurtosis containers
docker ps -a --filter "label=app.kubernetes.io/managed-by=kurtosis" --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}"
# If no label filter works, grep for kurtosis
docker ps -a | grep kurtosis
Engine issues
Engine won't start
# Check if old engine is still running
docker ps -a | grep kurtosis-engine
# Check engine logs
docker logs $(docker ps -aq --filter "name=kurtosis-engine") 2>&1 | tail -50
# Nuclear option: stop and remove all kurtosis containers
kurtosis engine stop
docker ps -a | grep kurtosis | awk '{print $1}' | xargs -r docker rm -f
kurtosis engine start
Engine version mismatch
# Check CLI version
kurtosis version
# Check running engine version
kurtosis engine status
# Force restart with matching version
kurtosis engine restart
Enclave / API container issues
The API container (core/APIC) runs inside each enclave and manages services.
# List enclaves
kurtosis enclave ls
# Find the APIC container for an enclave
docker ps -a | grep "kurtosis-api"
# View APIC logs (most useful for debugging enclave creation failures)
docker logs $(docker ps -aq --filter "name=kurtosis-api") 2>&1 | tail -100
Service debugging
# List services in an enclave
kurtosis enclave inspect <enclave-name>
# View service logs
kurtosis service logs <enclave-name> <service-name>
# Follow logs in real time
kurtosis service logs <enclave-name> <service-name> -f
# Shell into a running service
kurtosis service shell <enclave-name> <service-name>
# Execute a command in a service
kurtosis service exec <enclave-name> <service-name> -- <command>
Port and networking issues
# Check mapped ports for a service
kurtosis enclave inspect <enclave-name>
# Verify port is actually listening inside the container
kurtosis service exec <enclave-name> <service-name> -- netstat -tlnp
# Test connectivity between services (from inside a service)
kurtosis service exec <enclave-name> <service-name> -- wget -qO- http://<other-service>:<port>/endpoint
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.
- 3d ago First seen · 138 lines · 45 tokens per session scan A 1344b527281c
docker-debug is a skill published in the GitHub repository kurtosis-tech/kurtosis (550 stars, last pushed 8d ago), licensed Apache-2.0. It adds 45 tokens to every session and 989 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
new-service
Add a new service to Harbor — scaffold the compose config, environment variables, metadata, documentation, and cross-service integrations. Use this skill whenever the user wants to add a new service to Harbor, integrate a new tool/app/model server, create a compose configuration for a new project, or onboard any…
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.
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…
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…
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.