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/dumpnpx skills add kurtosis-tech/kurtosis --skill dumpgit 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/dump)<a href="https://agentmods.dev/skills/kurtosis-tech/kurtosis/dump"><img src="https://agentmods.dev/badge/skills/kurtosis-tech/kurtosis/dump.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.1 | $0.00046 | $0.00436 |
| Opus 5 | $0.00023 | $0.00218 |
| Sonnet 5 | $0.00009 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
dump 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 6d 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
Dump
Export Kurtosis state for debugging and sharing.
Dump entire Kurtosis state
kurtosis dump /tmp/kurtosis-dump
This exports everything: engine state, all enclaves, services, logs.
Dump a specific enclave
kurtosis enclave dump <enclave-name> /tmp/enclave-dump
What gets exported
The dump directory contains:
- Service logs — stdout/stderr from each service
- Service configs — how each service was configured
- File artifacts — all files stored in the enclave
- Enclave metadata — creation time, status, parameters
Directory structure
/tmp/enclave-dump/
service-1/
spec.json # Service configuration
output.log # Service logs
service-2/
spec.json
output.log
files-artifacts/
artifact-name/
file1.yaml
file2.json
Common uses
Share a bug report
# Dump the problematic enclave
kurtosis enclave dump failing-enclave /tmp/bug-report
# Compress for sharing
tar czf bug-report.tar.gz -C /tmp bug-report
Compare two runs
kurtosis enclave dump run-1 /tmp/dump-1
kurtosis enclave dump run-2 /tmp/dump-2
diff -r /tmp/dump-1 /tmp/dump-2
Capture state before cleanup
# Dump everything before cleaning
kurtosis dump /tmp/pre-clean-dump
kurtosis clean -a
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.
- 6d ago First seen · 79 lines · 46 tokens per session scan A f403ce42a6fd
dump is a skill published in the GitHub repository kurtosis-tech/kurtosis (550 stars, last pushed 3d ago), licensed Apache-2.0. It adds 46 tokens to every session and 436 once invoked, about $0.0002 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
anneal
Use when the user wants to systematically fix AI code slop — duplicated logic, over-engineering, silent error swallowing, convention drift, cargo-cult patterns, and other LLM-introduced architectural decay — over a specified duration.
bughunt
Fully autonomous bug hunting pipeline — discover bugs in a scoped area using parallel subagents, independently triage each finding, fix confirmed issues with subagents, then audit all fixes against repo constraints and target platforms. Runs end-to-end without user interaction.
bugbash
Systematically explore and test any software project (CLI, API, Backend, Library, etc.) to find bugs, usability issues, and edge cases. Produces a structured report with full reproduction evidence (exact commands, inputs, logs, and tracebacks) for every issue.
docker-docs
Comprehensive Docker 28.x reference covering all features: installation, Dockerfile instructions, multi-stage builds, Docker Compose, networking, volumes, CLI commands, image management, registries, security best practices, CI/CD integration, debugging, and Kubernetes migration. Use whenever the user mentions Docker…
docker-management
Docker container lifecycle management, Dockerfile authoring, and debugging.
env-doctor
环境诊断技能 - 运行时检测、端口检查、服务健康、一键修复.