Agent skill

Volt Load Testing

by owenHochwald in owenHochwald/volt

Safely exercise and evaluate HTTP APIs with the Volt CLI, including authenticated requests, JSON bodies, staged load, machine-readable results, performance baselines, and before/after comparisons.

MPL-2.0Auto-check passedTesting & QA

Install Volt Load Testing

skills CLI
$ npx skills add owenHochwald/volt --skill volt-load-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install owenHochwald/volt volt-load-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/owenHochwald/volt.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/volt-load-testing .claude/skills/volt-load-testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
volt-load-testing
GitHub stars
141
Token cost
~1.2k tokens
SKILL.md length
555 words
Files
2
Skills in repo
2
Repo updated
First seen
Licence
MPL-2.0

At a glance

Safely exercise and evaluate HTTP APIs with the Volt CLI, including authenticated requests, JSON bodies, staged load, machine-readable results, performance baselines, and before/after comparisons.

  • Works in 8 steps: Verify that volt is on PATH and inspect… → Verify one functional request with the… → Run a five-request smoke test with one… → …
  • Reviewing an API and the user asks to load test
  • SKILL.md covers Establish scope, Follow the staged workflow, Build commands and Interpret results, plus 1 more section
  • Needs API_TOKEN

What it does

Volt Load Testing is an agent skill from owenHochwald/volt. Safely exercise and evaluate HTTP APIs with the Volt CLI, including authenticated requests, JSON bodies, staged load, machine-readable results, performance baselines, and before/after comparisons. Use when developing or reviewing an API and the user asks to load test, benchmark, measure latency or throughput, check behavior under concurrency, investigate performance regressions, or run Volt.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Testing & QA, covering Load testing and REST APIs. The repository describes itself as: High-performance, concurrent, terminal-based HTTP client. The licence is MPL-2.0.

When your agent uses it

  • Reviewing an API and the user asks to load test
  • Measure latency
  • Check behavior under concurrency
  • Investigate performance regressions

Example prompts

  • “/volt-load-testing”

Requirements

  • A credential in API_TOKEN

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Verify that volt is on PATH and inspect volt bench -h.
  2. Verify one functional request with the service's tests or curl. Volt does not
  3. Run a five-request smoke test with one connection and -rate 1.
  4. Inspect the JSON result before increasing traffic.
  5. Run an unrecorded warm-up.
  6. Run a representative, explicitly rate-limited baseline.
  7. Increase load only when the user requested it and the prior stage remained
  8. Save JSON evidence and report the workload with secrets redacted.

What it can do on your machine

Read from SKILL.md and the folder at commit 35e1ad9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • API_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Volt Load Testing loads about 1.2k tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 555 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~103
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from owenHochwald/volt at commit 35e1ad9, republished under its MPL-2.0 licence (© owenHochwald). 555 words, ~1,193 tokens.

Download SKILL.mdSave it as .claude/skills/volt-load-testing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
volt-load-testing
description
Safely exercise and evaluate HTTP APIs with the Volt CLI, including authenticated requests, JSON bodies, staged load, machine-readable results, performance baselines, and before/after comparisons. Use when developing or reviewing an API and the user asks to load test, benchmark, measure latency or throughput, check behavior under concurrency, investigate performance regressions, or run Volt.

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

  1. Verify that volt is on PATH and inspect volt bench -h.
  2. Verify one functional request with the service's tests or curl. Volt does not currently provide a CLI single-request preflight.
  3. Run a five-request smoke test with one connection and -rate 1.
  4. Inspect the JSON result before increasing traffic.
  5. Run an unrecorded warm-up.
  6. Run a representative, explicitly rate-limited baseline.
  7. Increase load only when the user requested it and the prior stage remained healthy.
  8. 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:

bash
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

For a duration-based baseline:

bash
volt bench \
  -url http://127.0.0.1:8080/api/widgets \
  -m GET \
  -H "Authorization: Bearer ${API_TOKEN}" \
  -c 10 \
  -d 30s \
  -rate 100 \
  -t 5s \
  -json \
  -o volt-baseline.json

Use -n for a fixed count or -d for a time window; they are mutually exclusive. Treat -rate 0 as unlimited. Keep-alive is enabled unless -no-keepalive is set. Repeat -H for multiple headers.

The current CLI accepts only an inline body. Keep payloads in a file while editing and expand them at invocation. Note that expanded headers and bodies can be visible in the process list on a shared machine; tell the user when this limitation matters.

Show full SKILL.md (208 more words)Show less

Interpret results

Read these JSON fields:

  • summary.completedRequests, failedRequests, successRate, throughput, and durationMs
  • latency.minMs, avgMs, p50Ms, p90Ms, p95Ms, p99Ms, and maxMs
  • statusCodes and errors
  • transfer.bytesSent and bytesReceived

A completed Volt command currently exits successfully even if HTTP requests failed. Inspect failedRequests, status codes, and errors rather than treating a zero process exit code as a passing test.

Report:

  • authorized environment and code revision;
  • exact method, path, concurrency, rate, duration or count, timeout, and keep-alive mode, with secrets redacted;
  • completed requests, failures, achieved throughput, p50, p95, and p99;
  • status and error breakdowns;
  • whether each user-supplied objective was met; and
  • measurement limitations, especially shared CPU on a local target.

For before/after comparisons, keep the environment, request, data, concurrency, rate, execution bound, timeout, keep-alive behavior, and warm-up identical. Preserve both JSON files. Avoid claiming significance from a single small difference.

Handle failures

  • If the functional preflight fails, diagnose it before load testing.
  • If the target or authorization is ambiguous, do not send load; ask for the missing scope.
  • If the token is absent, report the environment variable name without asking the user to paste its value.
  • If the smoke test has failures, stop and report its JSON breakdown.
  • If no objective exists, return measurements and recommended next experiments, not an invented verdict.

© owenHochwald, MPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/volt-load-testing of owenHochwald/volt.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 35e1ad9

Compare with similar skills

Volt Load Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Volt Load Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Volt Load Testing this skillowenHochwald/volt141—~1.2kAutomated safety check: PassMPL-2.0
Writing Livekit Scenarioslivekit-examples/agent-starter-python2641 repos~2.5kAutomated safety check: PassMIT
Go Testingcxuu/golang-skills1701 repos~1.3kAutomated safety check: PassApache-2.0
Goalcraftgrp06/goalcraft102—~3.8kAutomated safety check: PassMIT
Thinking Partnermattnowdev/thinking-partner205—~4.4kAutomated safety check: PassMIT
Challengeblueberrycongee/termcanvas406—~1.5kAutomated safety check: PassMIT

Similar skills

  • Writing Livekit Scenarios

    livekit-examples/agent-starter-python

    Creates and maintains the scenarios a LiveKit agent simulation runs, and wires the agent to consume them.

    264 GitHub starsUsed in 1 repo~2.5k tokens
    Testing & QAAuto-check passed
  • Go Testing

    cxuu/golang-skills

    A skill your agent uses when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff.

    170 GitHub starsUsed in 1 repo~1.3k tokens
    Testing & QAAuto-check passed
  • Goalcraft

    grp06/goalcraft

    Turn a rough draft, vague ambition, or messy task brief into a powerful Codex /goal objective for persistent, evidence-checked work.

    102 GitHub stars~3.8k tokensUpdated 4 mo ago
    Testing & QAAuto-check passed
  • Thinking Partner

    mattnowdev/thinking-partner

    A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly.

    205 GitHub stars~4.4k tokensUpdated 6 mo ago
    Testing & QAAuto-check passed
  • Challenge

    blueberrycongee/termcanvas

    Adversarial review skill. An agent skill from blueberrycongee/termcanvas.

    406 GitHub stars~1.5k tokensUpdated 4 mo ago
    Testing & QAAuto-check passed
  • Vision

    kunchenguid/vision

    Draft and stress-test a VISION.md for a repository, then iterate with the author on an interactive review board until approved.

    329 GitHub stars~2.9k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

More from owenHochwald/volt

  • Volt UI Design

    owenHochwald/volt

    Design, implement, or review Volt's Bubble Tea and Lip Gloss terminal UI using the repository's Controlled Voltage design system.

    141 GitHub stars~820 tokensUpdated 2 mo ago
    Auto-check passed

Categories

Questions about Volt Load Testing

What does Volt Load Testing do?

Safely exercise and evaluate HTTP APIs with the Volt CLI, including authenticated requests, JSON bodies, staged load, machine-readable results, performance baselines, and before/after comparisons. Volt Load Testing is an agent skill from owenHochwald/volt. Safely exercise and evaluate HTTP APIs with the Volt CLI, including authenticated requests, JSON bodies, staged load, machine-readable results, performance baselines, and before/after comparisons.

When should I use Volt Load Testing?

Volt Load Testing fits situations like: reviewing an API and the user asks to load test; measure latency; check behavior under concurrency; investigate performance regressions.

How do I install Volt Load Testing in Claude Code?

Run `npx skills add owenHochwald/volt --skill volt-load-testing -a claude-code`. Or copy the skill folder (skills/volt-load-testing in owenHochwald/volt) into .claude/skills/volt-load-testing in your project. Claude Code loads it when a task matches its description.

How do I install Volt Load Testing in Codex?

Run `npx skills add owenHochwald/volt --skill volt-load-testing -a codex`. Or copy the skill folder (skills/volt-load-testing in owenHochwald/volt) into .agents/skills/volt-load-testing in your project. Codex loads it when a task matches its description.

Can I use Volt Load Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add owenHochwald/volt --skill volt-load-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/volt-load-testing, .gemini/skills/volt-load-testing, .github/skills/volt-load-testing and .opencode/skills/volt-load-testing in your project.

What does Volt Load Testing need to run?

Going by SKILL.md and its folder, Volt Load Testing needs credentials named API_TOKEN. Our summary lists: A credential in API_TOKEN.

Does Volt Load Testing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Volt Load Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Volt Load Testing use?

Volt Load Testing is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Volt Load Testing use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Volt Load Testing?

Skills that share tags, products or a category with Volt Load Testing: Writing Livekit Scenarios (livekit-examples/agent-starter-python, 264 stars), Go Testing (cxuu/golang-skills, 170 stars), Goalcraft (grp06/goalcraft, 102 stars) and Thinking Partner (mattnowdev/thinking-partner, 205 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Volt Load Testing?

owenHochwald (a GitHub user) maintains it in owenHochwald/volt, which has 141 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on July 25, 2026.

Source: owenHochwald/volt on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.