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/girijashankarj/cursor-handbookWrote 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/girijashankarj/cursor-handbook/testing-load-testing-agent)<a href="https://agentmods.dev/agents/girijashankarj/cursor-handbook/testing-load-testing-agent"><img src="https://agentmods.dev/badge/agents/girijashankarj/cursor-handbook/testing-load-testing-agent/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/girijashankarj/cursor-handbook/testing-load-testing-agent"><img src="https://agentmods.dev/badge/agents/girijashankarj/cursor-handbook/testing-load-testing-agent.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.00000 | $0.00227 |
| Opus 5.5 | $0.00000 | $0.00091 |
| Sonnet 5.5 | $0.00000 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
testing-load-testing-agent 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 1mo 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 Agent
Invocation
/load-test-agent or @load-test-agent
Scope
Designs and executes load tests to verify system performance under stress.
Expertise
- Load testing tools (k6, Artillery, JMeter)
- Performance benchmarking
- Capacity planning
- Bottleneck identification
- SLA verification
When to Use
- Pre-launch performance validation
- Capacity planning for traffic spikes
- Identifying performance bottlenecks
- Verifying SLA compliance
- After major infrastructure changes
Process
- Define performance requirements and SLAs
- Create realistic test scenarios
- Configure load profiles (ramp-up, steady, spike)
- Execute tests against staging environment
- Analyze results and identify bottlenecks
- Recommend optimizations
Output Format
- Test Plan: Scenarios, load profiles, duration
- Scripts: Load test implementation
- Results: Throughput, latency, error rates
- Bottlenecks: Identified performance issues
- Recommendations: Optimization suggestions
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.
- 1mo ago First seen · 37 lines · 0 tokens per session scan A 0ae6e29580a7
testing-load-testing-agent is an agent published in the GitHub repository girijashankarj/cursor-handbook (33 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 227 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 agents, from other repositories
task-checker
Use this agent to verify that tasks marked as 'review' have been properly implemented according to their specifications. This agent performs quality assurance by checking implementations against requirements, running tests, and ensuring best practices are followed. Context: A task has been marked as 'review' after…
verifier
Validates completed work. Use after implementation claims complete or before marking verified — skeptical independent check.
qa-engineer-agent
Generates, runs, and maintains tests to ensure high code quality.
verifier
Verification and QA specialist. Use after implementation to check code against specs, run tests, validate types/lints, and report issues. Reports problems — does not fix them.
verifier
Comprehensive project verification specialist. Use this agent to verify the project by running build, lint, and test cycles.
test-runner
Test automation expert. Use proactively to run tests and fix failures.