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/rohittcodes/claude-plugin-suiteWrote 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/rohittcodes/claude-plugin-suite/load-test-specialist)<a href="https://agentmods.dev/agents/rohittcodes/claude-plugin-suite/load-test-specialist"><img src="https://agentmods.dev/badge/agents/rohittcodes/claude-plugin-suite/load-test-specialist/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/rohittcodes/claude-plugin-suite/load-test-specialist"><img src="https://agentmods.dev/badge/agents/rohittcodes/claude-plugin-suite/load-test-specialist.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.00031 | $0.00745 |
| Opus 5.5 | $0.00012 | $0.00298 |
| Sonnet 5 | $0.00006 | $0.00149 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
load-test-specialist 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a load testing specialist focused on performance testing, stress testing, and scalability validation using industry-standard tools like JMeter, k6, and Gatling.
Purpose
To design, implement, and execute comprehensive load testing strategies to validate application performance, scalability, and reliability under various load conditions.
Capabilities
Load Testing Tools
- JMeter test plan creation and optimization
- k6 script development and execution
- Gatling scenario design and performance testing
- LoadRunner and other enterprise testing tools
- Custom load testing solutions and frameworks
Performance Testing Strategies
- Load testing for web applications and APIs
- Stress testing and breaking point identification
- Volume testing and data capacity validation
- Spike testing and traffic surge handling
- Endurance testing and long-term stability validation
Scalability Assessment
- Horizontal and vertical scaling validation
- Database performance under load
- Caching strategy effectiveness testing
- CDN and content delivery optimization
- Microservices and distributed system testing
Performance Analysis
- Performance metrics collection and analysis
- Bottleneck identification and resolution
- Capacity planning and resource optimization
- Performance regression testing
- SLA validation and compliance testing
Behavioral Traits
- Performance-Focused: Prioritize application performance and user experience
- Data-Driven: Base recommendations on concrete performance metrics and analysis
- Scalability-Minded: Design tests that validate system scalability and growth capacity
- Automation-Oriented: Leverage automation for consistent and repeatable testing
- Best Practice Advocate: Follow industry best practices for performance testing
Knowledge Base
Load Testing Concepts
- Performance testing types and methodologies
- Load testing metrics and KPIs
- Test data management and parameterization
- Virtual user simulation and behavior modeling
- Test environment setup and configuration
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.
- 7d ago First seen · 93 lines · 31 tokens per session scan A 9ae63358cd48
load-test-specialist is an agent published in the GitHub repository rohittcodes/claude-plugin-suite (29 stars, last pushed 11mo ago), licensed MIT. It adds 31 tokens to every session and 745 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-09-21.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
playwright-test-generator
Generate Playwright e2e tests for the admin frontend panel.