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 run-packagegit 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/run-package)<a href="https://agentmods.dev/skills/kurtosis-tech/kurtosis/run-package"><img src="https://agentmods.dev/badge/skills/kurtosis-tech/kurtosis/run-package/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/run-package"><img src="https://agentmods.dev/badge/skills/kurtosis-tech/kurtosis/run-package.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.00051 | $0.00883 |
| Opus 5 | $0.00026 | $0.00441 |
| Sonnet 5 | $0.00010 | $0.00177 |
| Haiku 4.5 | $0.00005 | $0.00088 |
Grade A, and why
run-package 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 9d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Package
Execute Starlark scripts and packages with kurtosis run.
Basic usage
# Run a local package
kurtosis run ./my-package
# Run a local .star script
kurtosis run ./script.star
# Run a remote package from GitHub
kurtosis run github.com/ethpandaops/ethereum-package
# Run with inline args
kurtosis run github.com/ethpandaops/ethereum-package '{"participants": [{"el_type": "geth", "cl_type": "lighthouse"}]}'
# Run with args from a file (JSON or YAML)
kurtosis run github.com/ethpandaops/ethereum-package --args-file config.yaml
Named enclaves
# Run in a specific enclave (created if it doesn't exist)
kurtosis run --enclave my-testnet github.com/ethpandaops/ethereum-package
# Re-run in an existing enclave (adds to it)
kurtosis run --enclave my-testnet ./additional-services.star
Dry run
Preview what will execute without making changes:
kurtosis run --dry-run github.com/ethpandaops/ethereum-package --args-file config.yaml
Verbosity levels
# Default — concise description of what happens
kurtosis run ./my-package
# Brief — concise but explicit
kurtosis run -v brief ./my-package
# Detailed — all arguments for each instruction
kurtosis run -v detailed ./my-package
# Executable — generates copy-pasteable Starlark
kurtosis run -v executable ./my-package
# Output only — just the return value
kurtosis run -v output_only ./my-package
Image handling
# Default: only pull if image doesn't exist locally
kurtosis run ./my-package
# Always pull latest image tags
kurtosis run --image-download always ./my-package
Parallel execution
# Run instructions in parallel (as soon as dependencies resolve)
kurtosis run --parallel ./my-package
# Set parallelism level
kurtosis run --parallel --parallelism 8 ./my-package
Advanced options
# Production mode — services auto-restart on failure
kurtosis run -p ./my-package
# Custom entry point file
kurtosis run --main-file deploy.star ./my-package
# Custom main function
kurtosis run --main-function-name setup ./my-package
# Don't forward ports locally
kurtosis run --no-connect ./my-package
# Show dependency graph
kurtosis run --output-graph ./my-package
# List image and package dependencies
kurtosis run --dependencies ./my-package
# Pull all dependencies locally
kurtosis run --pull --dependencies ./my-package
# Skip enclave inspect output
kurtosis run --show-enclave-inspect=false ./my-package
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.
- 9d ago First seen · 142 lines · 51 tokens per session scan A 02708c7d727e
run-package is a skill published in the GitHub repository kurtosis-tech/kurtosis (551 stars, last pushed 5d ago), licensed Apache-2.0. It adds 51 tokens to every session and 883 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-daytona
Use Harbor's Daytona sandbox platform for computer use — creating sandboxes, taking screenshots, sending mouse/keyboard input, and building agent loops. Use when the user wants to interact with a GUI, automate a desktop, do computer use, control a browser visually, or run Claude computer use against a Daytona sandbox.
boost-modules
Skill "boost-modules" from av/harbor, covering harbor boost custom modules, module structure, quick reference, output methods and stream text to client.
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…
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…