A skill for testing how an HTTP API behaves under many requests at once. It measures response speed, request volume, and failures, including common latency percentiles such as p95 and p99.

Use it to run, stop, and inspect concurrent or rate-controlled tests against an API endpoint, with optional headers and time limits.

It shows whether an API slows down or starts failing under expected or heavy traffic instead of relying on a single manual request.

load-test — Skill by fisker086

Install

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.

agentmods

npx agentmods add skills/fisker086/aiops/load_test

Any agent

npx skills add fisker086/AIOps --skill load_test

Clone the repo

git clone --depth 1 https://github.com/fisker086/AIOps

Made for: Claude Code, Codex.

Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 236 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00010	$0.00236
Opus 5	$0.00005	$0.00118
Sonnet 5	$0.00002	$0.00047
Haiku 4.5	$0.00001	$0.00024

Measured 3d ago against content hash 1e1cdeb221c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

load-test 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 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.

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.

skills/load_test/SKILL.md · 34 lines

What it actually says

Load Test Skill

Perform HTTP API load and performance testing:

Concurrent requests simulation
Request rate control (RPS)
Duration-based or count-based tests
Latency percentiles (p50, p95, p99)
Throughput metrics (requests/sec)
Error rate calculation

Use builtin_load_test tool with fields:

operation: "run" | "stop" | "results"
url: Target endpoint URL
method: HTTP method (default: GET)
concurrency: Number of concurrent users
requests: Total number of requests
duration: Test duration in seconds
rate: Target requests per second
headers: (optional) Request headers as JSON

Returns:

Total/Successful/Failed requests
Average/Min/Max latency
Percentiles (p50, p90, p95, p99)
Requests per second
Error rate percentage

Changes

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 · 34 lines · 10 tokens per session scan A 1e1cdeb221c2

Subscribe to this mod's changes

load-test is a skill published in the GitHub repository fisker086/AIOps (21 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 236 once invoked, about $0.0001 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.

Backend and APIs Testing

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens