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/commands/rohittcodes/claude-plugin-suite/performance-test)<a href="https://agentmods.dev/commands/rohittcodes/claude-plugin-suite/performance-test"><img src="https://agentmods.dev/badge/commands/rohittcodes/claude-plugin-suite/performance-test/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/commands/rohittcodes/claude-plugin-suite/performance-test"><img src="https://agentmods.dev/badge/commands/rohittcodes/claude-plugin-suite/performance-test.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.00006 | $0.00377 |
| Opus 5.5 | $0.00002 | $0.00151 |
| Sonnet 5 | $0.00001 | $0.00075 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
performance-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 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.
What it actually says
Performance Testing Command
Execute comprehensive performance testing and optimization analysis with detailed metrics.
Context
- Test scenario: $1 (load|stress|spike|endurance - default: load)
- Load level: $2 (light|medium|heavy|extreme - default: medium)
- Application endpoints: @src/routes
- Performance baseline: @performance-baseline.json
Performance Testing Strategy
1. Load Testing
- Simulate normal user traffic
- Measure response times and throughput
- Validate system stability
- Identify performance bottlenecks
2. Stress Testing
- Push system beyond normal capacity
- Identify breaking points
- Test system recovery
- Validate error handling
3. Performance Analysis
- Response time analysis
- Throughput measurement
- Resource utilization monitoring
- Database performance assessment
4. Optimization Recommendations
- Performance bottleneck identification
- Scalability improvement suggestions
- Resource optimization strategies
- Caching implementation guidance
Performance Metrics
- Response time (p50, p95, p99)
- Throughput (requests per second)
- Error rate and availability
- Resource utilization (CPU, memory, disk)
Expected Outcome
- Detailed performance test report
- Performance metrics and benchmarks
- Bottleneck identification and analysis
- Actionable optimization recommendations
Performance Thresholds
- Response time: < 200ms (p95)
- Throughput: > 1000 RPS
- Error rate: < 0.1%
- Availability: > 99.9%
Failure Analysis
If performance targets not met:
- Root cause analysis
- Performance optimization plan
- Infrastructure scaling recommendations
- Code 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.
- 7d ago First seen · 66 lines · 0 tokens per session scan A 3853fe80d480
performance-test is a command published in the GitHub repository rohittcodes/claude-plugin-suite (29 stars, last pushed 11mo ago), licensed MIT. It adds 6 tokens to every session and 377 once invoked, about $0.0000 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 commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
verify
Run repository verification using the verification-loop skill.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.