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 skills add int2t05/engineering-skills --skill load-testinggit clone --depth 1 https://github.com/int2t05/engineering-skillsWrote 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/int2t05/engineering-skills/load-testing)<a href="https://agentmods.dev/skills/int2t05/engineering-skills/load-testing"><img src="https://agentmods.dev/badge/skills/int2t05/engineering-skills/load-testing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/int2t05/engineering-skills/load-testing"><img src="https://agentmods.dev/badge/skills/int2t05/engineering-skills/load-testing.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00021 | $0.00294 |
| Opus 5.5 | $0.00008 | $0.00118 |
| Sonnet 5.5 | $0.00004 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
load-testing 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 8d 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
Load Testing
When to use
- Measure capacity under authorized representative traffic.
Not for: performance for bottlenecks; api-testing for correctness.
Steps
-
Agree environment, traffic budget, load targets and stop conditions; do not assume production access.
-
Build runnable scripts with realistic operations, datasets and arrivals; check functional responses first.
-
Run relevant ramp, sustained, burst or stress profiles and observe latency, errors and saturation within agreed limits.
-
Identify bottlenecks and recovery and record reproducible conditions in the approved capacity report.
Output: Suggested paths, subject to human audit: docs/CAPACITY.md for durable capacity decisions.
Verify
- Scripts and actual measurements exist; errors and saturation inform conclusions and untested autoscaling remains unverified.
References
- engineering-principles.md — shared decision boundaries, scope and verification.
- human-audit.md — document consent, readability and human review.
- references/load-profiles.md — traffic-mix modeling, test-pattern catalog (ramp/soak/spike/stress), breaking-point characterization, autoscaling validation checklist
What ships with it
2 files 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.
- 8d ago Changed · -93 lines · -44 tokens per session 5120fde75261
- 15d ago Changed · +3 lines 05fca10ccee7
- 1mo ago First seen · 125 lines · 65 tokens per session scan A e201b59c75d6
load-testing is a skill published in the GitHub repository int2t05/engineering-skills (3 stars, last pushed 9d ago), licensed MIT. It adds 21 tokens to every session and 294 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
plan
Analyzes architecture, selects patterns, assesses testability, then decomposes work into ordered TDD tasks with exact verification commands and explicit acceptance mapping. Works from an approved spec (zuvo:brainstorm output) or directly from a user-provided description.
test-audit
Audit test suites for T1-T4 violations using AST analysis, mock detection, and multi-stage synthesis. Invoke when user asks to audit tests, check test quality, find mock violations, review test effectiveness, or inspect test suites for over-mocking. Triggers automatic rewrites when quality gates fail.
Eval-Driven Skill Design
A review guide for new coding-agent skills that checks whether each skill has both examples it should catch and examples it should ignore, plus evaluation setup.
x-qdev
A compact development workflow for a small, clearly defined code change. It keeps the requirement, initially failing tests, implementation, and real verification results in one task document, following TDD, or test-driven development.
Component Test Scaffold (Next.js)
Generate React/Next.js component test skeletons (RTL) from specifications.
Test Scaffold (Laravel/PHPUnit)
Generate PHP/Laravel (PHPUnit) test skeletons from specifications.