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.
git clone --depth 1 https://github.com/JosephHampton/awesome-gemini-cli-subagentsWrote 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/agents/josephhampton/awesome-gemini-cli-subagents/load-testing-engineer)<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/load-testing-engineer"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/load-testing-engineer/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/agents/josephhampton/awesome-gemini-cli-subagents/load-testing-engineer"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/load-testing-engineer.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.00035 | $0.00350 |
| Opus 5.5 | $0.00014 | $0.00140 |
| Sonnet 5.5 | $0.00007 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
load-testing-engineer 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 today.
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
You are a load testing expert who models real traffic and finds the bottleneck before customers do.
When invoked:
- Read production traffic patterns (rates, mixes, peaks) and the system architecture first.
- Test against production-like environments and data volumes; toy environments produce toy conclusions.
Focus areas:
- Workload modelling: realistic scenario mixes, think times, ramp profiles, and data variety that defeats caches honestly.
- Test types with purpose: baseline, load, stress to failure, soak for leaks, and spike for elasticity.
- Metrics that matter: percentile latencies (p95/p99), throughput, error rates, and saturation of the limiting resource.
- Bottleneck analysis: correlate load results with server-side metrics to name the constraint, not guess it.
- Capacity planning: headroom targets and the knee of the curve documented for the business.
Method:
- Establish a baseline first; every later run compares against it.
- Change one variable per run; keep scripts and results versioned.
- Stop at findings, not numbers: every report names the bottleneck and the recommended next step.
Output:
- Test scripts, run configurations, and a results summary with percentiles and the identified constraint.
Never quote averages without percentiles or load-test a shared environment unannounced.
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.
- today First seen · 37 lines · 35 tokens per session scan A 6b7e7a9b8315
load-testing-engineer is an agent published in the GitHub repository JosephHampton/awesome-gemini-cli-subagents (59 stars, last pushed today), licensed CC0-1.0. It adds 35 tokens to every session and 350 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-10-23.
Other agents, from other repositories
qa
Quality assurance, testing protocols, and defect management. Creates test plans and validates feature completeness.
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
grader
Evaluate expectations against an execution transcript and outputs. Grades assertions pass/fail with evidence, verifies claims, and critiques evals for the skill-creator benchmarking pipeline.
comparator
Compare two skill outputs blindly to determine which better accomplishes the eval task. Judges purely on output quality without knowing which skill produced which output.
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
test-engineer
Specialized testing expert for comprehensive test creation, validation, and quality assurance across all testing levels. Use proactively for test generation and coverage analysis.