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/owenhochwald/volt/volt-load-testingnpx skills add owenHochwald/volt --skill volt-load-testinggit clone --depth 1 https://github.com/owenHochwald/voltWhat 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.00076 | $0.01120 |
| Opus 5 | $0.00038 | $0.00560 |
| Sonnet 5 | $0.00015 | $0.00224 |
| Haiku 4.5 | $0.00008 | $0.00112 |
Grade A, and why
volt-load-testing scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Read route definitions, an OpenAPI document, tests, or an existing curl How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Volt Load Testing
Use Volt's non-interactive bench command. Treat load generation as a
potentially disruptive operation and keep every run authorized and bounded.
Establish scope
Before sending traffic:
- Confirm that the user owns the target or is authorized to test it.
- Prefer localhost, a preview environment, or a dedicated test environment.
- Do not test production, shared infrastructure, or a third-party API without explicit approval and a traffic budget.
- Determine whether the request mutates data. Use disposable data and verify that repeating it is safe.
- Read route definitions, an OpenAPI document, tests, or an existing curl example to obtain the URL, uppercase method, headers, body, and expected successful statuses.
- Use a user-provided service objective. If none exists, report a baseline without declaring it a pass or failure.
Never paste, print, or commit a secret. Refer to a credential already supplied
through an environment variable, such as ${API_TOKEN}.
Follow the staged workflow
- Verify that
voltis onPATHand inspectvolt bench -h. - Verify one functional request with the service's tests or curl. Volt does not currently provide a CLI single-request preflight.
- Run a five-request smoke test with one connection and
-rate 1. - Inspect the JSON result before increasing traffic.
- Run an unrecorded warm-up.
- Run a representative, explicitly rate-limited baseline.
- Increase load only when the user requested it and the prior stage remained healthy.
- Save JSON evidence and report the workload with secrets redacted.
Do not jump directly to unlimited traffic. Stop when failures rise unexpectedly or the target becomes unhealthy.
Build commands
Use the explicit subcommand and JSON output:
volt bench \
-url http://127.0.0.1:8080/api/widgets \
-m POST \
-H "Authorization: Bearer ${API_TOKEN}" \
-H "Content-Type: application/json" \
-b "$(<request.json)" \
-c 1 \
-n 5 \
-rate 1 \
-json \
-o volt-smoke.json
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 127 lines · 76 tokens per session scan A c7f460af9aff
volt-load-testing is a skill published in the GitHub repository owenHochwald/volt (141 stars, last pushed 1mo ago), licensed MPL-2.0. It adds 76 tokens to every session and 1,120 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.