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/the-void-ia/void-box/test-vmnpx skills add the-void-ia/void-box --skill test-vmgit clone --depth 1 https://github.com/the-void-ia/void-boxWrote 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/the-void-ia/void-box/test-vm)<a href="https://agentmods.dev/skills/the-void-ia/void-box/test-vm"><img src="https://agentmods.dev/badge/skills/the-void-ia/void-box/test-vm.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.00026 | $0.01527 |
| Opus 5 | $0.00013 | $0.00763 |
| Sonnet 5 | $0.00005 | $0.00305 |
| Haiku 4.5 | $0.00003 | $0.00153 |
Grade C, and why
test-vm scanned grade C with 2 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 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
If not installed: macOS → `brew install ollama`; Linux → `curl -fsSL https://ollama.com/install.sh | sh`. Stop until installed. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
If not installed: macOS → `brew install ollama`; Linux → `curl -fsSL https://ollama.com/install.sh | sh`. Stop until installed. How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Runs examples/smoke/smoke.yaml — the agent replies with "vm-ok 2+2=4". No tool use required; any model that generates text will pass. Success is success: true with output containing vm-ok.
All commands run from the repository root.
Usage: /test-vm [ollama [model] | claude | claude-personal]
ollama [model]— local Ollama (default model:phi4-mini)claude— Anthropic API key (ANTHROPIC_API_KEYmust be set)claude-personal— personal Claude account (macOS: extracted from Keychain; Linux: staged from~/.claude/)- no argument — defaults to
ollama phi4-mini
Recommended Ollama models (2–4 GB RAM, reliable with claude-code): phi4-mini, gemma3:4b, llama3.2:3b. Avoid *-coder variants — they don't follow the agentic protocol well.
Step 1 — Prerequisites
Kernel
Check for an existing kernel file. macOS needs an uncompressed kernel (vmlinux-*); Linux can use the host kernel (vmlinuz-*):
ls target/vmlinux-arm64 2>/dev/null \
|| ls target/vmlinux-amd64 2>/dev/null \
|| ls /boot/vmlinuz-$(uname -r) 2>/dev/null \
|| echo "MISSING"
If missing, download it (the script caches the result in target/):
scripts/download_kernel.sh
After downloading, run the check again to confirm and record the path — it is needed in Step 4.
Rootfs
ls target/void-box-rootfs.cpio.gz 2>/dev/null || echo "MISSING"
If missing, build it (auto-detects the claude binary on PATH or ~/.local/bin/claude):
scripts/build_claude_rootfs.sh
Run the check again to confirm. If it still fails, tell the user to set CLAUDE_BIN=/path/to/claude and retry.
Step 2 — Build and sign
cargo build --release --bin voidbox
macOS only — Apple Virtualization.framework requires the entitlement:
codesign --force --sign - --entitlements voidbox.entitlements target/release/voidbox
Step 3 — Provider setup
Ollama
Check Ollama is installed:
which ollama || echo "NOT INSTALLED"
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 · 174 lines · 26 tokens per session scan C fb047974eec2
test-vm is a skill published in the GitHub repository the-void-ia/void-box (88 stars, last pushed 6d ago), licensed Apache-2.0. It adds 26 tokens to every session and 1,527 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, 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
opentelemetry-net-instrumentation
Provides guidance for implementing OpenTelemetry instrumentation in .NET codebases, covering tracing (Activities/Spans), metrics, logs, naming conventions, error handling, performance, SDK setup, resources, context propagation, and API design best practices.
clawmetry-selfcheck
Read your own agent telemetry from ClawMetry (waste, progress, cost) and act on it before finishing a task. Use when ClawMetry is installed on this machine and you want to check whether you are re-reading files, spinning in loops, or burning budget.
migrate-state-management
Migrate Redux or React Context to the correct state option (React Query for server state, nuqs for URL/shareable state, Zustand for global client state). Use when refactoring away from Redux/Context, moving state to the right store, or when the user asks to migrate state management.
clawmetry
Real-time observability for OpenClaw agents — local dashboard + optional encrypted cloud sync. Tracks costs, tokens, sessions, tool calls, memory, crons, and system health. Access from anywhere via ClawMetry Cloud.
otel-collector
OpenTelemetry Collector component configuration. Use when authoring, reviewing, or debugging Collector YAML for a specific receiver, processor, exporter, connector, or extension — config keys, defaults, validation rules, signal support, stability levels, and component-level gotchas. Triggers on Collector component…
otel-declarative-config
OpenTelemetry declarative YAML configuration for SDK setup. Use when configuring OpenTelemetry SDK providers (tracer, meter, logger), setting up OTLP exporters, defining sampling strategies, or writing otel config files. Triggers on "otel config", "OpenTelemetry YAML", "declarative configuration", "otelconf"…