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/profilenpx skills add the-void-ia/void-box --skill profilegit 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/profile)<a href="https://agentmods.dev/skills/the-void-ia/void-box/profile"><img src="https://agentmods.dev/badge/skills/the-void-ia/void-box/profile.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.00033 | $0.02123 |
| Opus 5 | $0.00016 | $0.01061 |
| Sonnet 5 | $0.00007 | $0.00425 |
| Haiku 4.5 | $0.00003 | $0.00212 |
Grade B, and why
profile scanned grade B 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
> sudo setcap 'cap_sys_admin,cap_bpf,cap_perfmon,cap_sys_ptrace,cap_checkpoint_restore=ep' $HOME/.local/bin/perf-agent Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
LATEST=$(curl -s https://api.github.com/repos/dpsoft/perf-agent/releases/latest | grep '"tag_name"' | cut -d'"' -f4) How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Profile a VoidBox Process
Profile CPU, off-CPU, and hardware counters using the eBPF-based perf-agent tool.
Prerequisites
Tell the user FIRST before doing anything else:
perf-agent requires Linux capabilities to run without sudo. Please run:
sudo setcap 'cap_sys_admin,cap_bpf,cap_perfmon,cap_sys_ptrace,cap_checkpoint_restore=ep' $HOME/.local/bin/perf-agent(Only needed once after each download.)
Note: The binary must NOT be on a
nosuidfilesystem (e.g./tmp), as file capabilities are silently ignored there.
Do NOT attempt to run sudo yourself. Ask the user and wait for confirmation.
Setup
Run these checks yourself (no sudo needed):
1. Detect architecture and download if needed:
ARCH=$(uname -m)
case "$ARCH" in
x86_64) SUFFIX="linux-amd64" ;;
aarch64) SUFFIX="linux-arm64" ;;
esac
mkdir -p "$HOME/.local/bin"
LATEST=$(curl -s https://api.github.com/repos/dpsoft/perf-agent/releases/latest | grep '"tag_name"' | cut -d'"' -f4)
if [ -x "$HOME/.local/bin/perf-agent" ]; then
CURRENT=$("$HOME/.local/bin/perf-agent" --version 2>/dev/null || echo "unknown")
if echo "$CURRENT" | grep -q "${LATEST#v}"; then
echo "perf-agent up-to-date ($LATEST)"
else
echo "Downloading perf-agent $LATEST..."
curl -fSL -o "$HOME/.local/bin/perf-agent" "https://github.com/dpsoft/perf-agent/releases/download/${LATEST}/perf-agent-${SUFFIX}"
chmod +x "$HOME/.local/bin/perf-agent"
fi
else
echo "Downloading perf-agent $LATEST..."
curl -fSL -o "$HOME/.local/bin/perf-agent" "https://github.com/dpsoft/perf-agent/releases/download/${LATEST}/perf-agent-${SUFFIX}"
chmod +x "$HOME/.local/bin/perf-agent"
fi
After download or upgrade, ask the user to run the setcap command.
2. Verify Go (required for pprof analysis):
go version
Find the PID
Auto-detect the running voidbox process:
pgrep -fa voidbox
If multiple processes, pick the voidbox shell one. If none found, tell the
user to start a voidbox process first.
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 · 211 lines · 33 tokens per session scan B e6425f1ad906
profile 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 33 tokens to every session and 2,123 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, 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"…