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 commands/rohitg00/awesome-claude-code-toolkit/load-testgit clone --depth 1 https://github.com/rohitg00/awesome-claude-code-toolkitWhat 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.00000 | $0.00483 |
| Opus 5 | $0.00000 | $0.00242 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00048 |
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.
What it actually says
Run a load test against an API endpoint to measure throughput and identify breaking points.
Steps
- Define load test parameters:
- Target URL and HTTP method.
- Concurrent connections (start low, ramp up).
- Duration of the test.
- Request payload and headers.
- Select the load testing tool:
wrkorwrk2for HTTP benchmarking.k6for scripted load tests.ab(Apache Bench) for simple tests.heyfor quick Go-based load tests.
- Run a warm-up phase with low concurrency (10 connections, 10 seconds).
- Execute the main load test in stages:
- Stage 1: Normal load (expected concurrent users).
- Stage 2: Peak load (2x expected).
- Stage 3: Stress test (increase until error rate > 5%).
- Collect metrics at each stage:
- Requests per second (throughput).
- Latency distribution (P50, P95, P99).
- Error rate and error types.
- Resource utilization (CPU, memory) if accessible.
- Identify the breaking point and bottleneck.
- Generate a report with recommendations.
Format
Load Test: <METHOD> <endpoint>
| Stage | Concurrency | RPS | P50 (ms) | P99 (ms) | Errors |
|-------|-------------|-----|----------|----------|--------|
| Normal | 10 | 500 | 20 | 85 | 0% |
| Peak | 50 | 1200 | 45 | 200 | 0.1% |
| Stress | 200 | 800 | 500 | 2000 | 5.2% |
Breaking point: ~150 concurrent connections
Bottleneck: Database connection pool exhaustion
Recommendations:
1. Increase connection pool size from 10 to 50
2. Add connection queuing with backpressure
Rules
- Never run load tests against production without explicit permission.
- Always include a warm-up phase before measuring.
- Ramp up gradually; do not jump to maximum load immediately.
- Record baseline metrics before the test for comparison.
- Stop the test if error rate exceeds 10% to avoid cascading failures.
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 · 54 lines · 0 tokens per session scan A b16d3fcfa95f
load-test is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,578 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 483 tokens. 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.
Other commands, from other repositories
run-plan
Execute a PLAN.md file directly without loading planning skill context.
check-todos
List outstanding todos and select one to work on.
audit-skill
Audit skill for YAML compliance, pure XML structure, progressive disclosure, and best practices.
create-agent-skill
Create or edit Claude Code skills with expert guidance on structure and best practices.
create-slash-command
Create a new slash command following best practices and patterns.
create-hook
Invoke create-hooks skill for expert guidance on Claude Code hook development.