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 files-inspectgit 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/files-inspect)<a href="https://agentmods.dev/skills/kurtosis-tech/kurtosis/files-inspect"><img src="https://agentmods.dev/badge/skills/kurtosis-tech/kurtosis/files-inspect/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/files-inspect"><img src="https://agentmods.dev/badge/skills/kurtosis-tech/kurtosis/files-inspect.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.01335 |
| Opus 5 | $0.00026 | $0.00668 |
| Sonnet 5 | $0.00010 | $0.00267 |
| Haiku 4.5 | $0.00005 | $0.00134 |
Grade A, and why
files-inspect 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 11d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Files Inspect
Work with Kurtosis file artifacts — the mechanism for passing files between services and into containers.
What are file artifacts?
File artifacts are named collections of files stored in an enclave. They're created by:
plan.upload_files()— upload local files from a packageplan.render_templates()— render Go templates with dataplan.store_service_files()— copy files from a running serviceplan.run_sh()/plan.run_python()— store output files from scripts
Services mount artifacts via the files parameter in ServiceConfig.
List artifacts in an enclave
kurtosis enclave inspect <enclave-name>
The "Files Artifacts" section shows each artifact's UUID and name:
========================================= Files Artifacts =========================================
UUID Name
4a0563e5a391 1-lighthouse-geth-0-127
f49b81f30a8f el_cl_genesis_data
88c3f17013f3 jwt_file
Download artifacts
# Download to a local directory
kurtosis files download <enclave-name> <artifact-name> /tmp/artifact-output
# Example: inspect genesis data
kurtosis files download <enclave-name> el_cl_genesis_data /tmp/genesis
ls -la /tmp/genesis/
cat /tmp/genesis/config.yaml
Upload files
# Upload a local file or directory as an artifact
kurtosis files upload <enclave-name> /path/to/local/file-or-dir
The command returns the artifact name and UUID for use in subsequent service configs.
Inspect files inside a running service
Verify files were mounted correctly by checking content matches expectations:
# List files at the mount path to confirm they exist
kurtosis service exec <enclave-name> <service-name> -- ls -la /mounted/path/
# Inspect file contents to verify correctness
kurtosis service exec <enclave-name> <service-name> -- cat /mounted/path/config.yaml
# Compare against expected content (e.g., check a key value)
kurtosis service exec <enclave-name> <service-name> -- sh -c "grep 'expected_key' /mounted/path/config.yaml"
# Or shell in for interactive exploration
kurtosis service shell <enclave-name> <service-name>
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.
- 11d ago First seen · 189 lines · 51 tokens per session scan A 66cb1b7bdb06
files-inspect is a skill published in the GitHub repository kurtosis-tech/kurtosis (551 stars, last pushed yesterday), licensed Apache-2.0. It adds 51 tokens to every session and 1,335 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
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
A diagnostic tool for checking a development environment, including runtimes, ports, and service health.
Pair Programming
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.