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 personamanagmentlayer/pcl --skill load-testing-expertgit clone --depth 1 https://github.com/personamanagmentlayer/pclWrote 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/personamanagmentlayer/pcl/load-testing-expert)<a href="https://agentmods.dev/skills/personamanagmentlayer/pcl/load-testing-expert"><img src="https://agentmods.dev/badge/skills/personamanagmentlayer/pcl/load-testing-expert.svg" alt="Measured on agentmods" 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.00075 | $0.01096 |
| Opus 5 | $0.00037 | $0.00548 |
| Sonnet 5 | $0.00015 | $0.00219 |
| Haiku 4.5 | $0.00007 | $0.00110 |
Grade A, and why
load-testing-expert 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 yesterday.
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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load Testing Expert
Core Concepts
Load Testing Types
- Load Testing - Expected load performance
- Stress Testing - Beyond capacity limits
- Spike Testing - Sudden load increases
- Soak Testing - Extended duration performance
- Scalability Testing - System growth capacity
- Volume Testing - Large data handling
Key Metrics
- Response Time - Request completion time
- Throughput - Requests per second (RPS)
- Error Rate - Percentage of failed requests
- Latency - Time to first byte (TTFB)
- Concurrent Users - Simultaneous active users
- Resource Utilization - CPU, memory, network
Tools & Frameworks
- Apache JMeter - Java-based load testing
- k6 - Modern JavaScript load testing
- Gatling - Scala-based performance testing
- Locust - Python-based load testing
- Artillery - Node.js load testing
- Vegeta - Go HTTP load testing
Best Practices
Test Design
- Start with baseline performance
- Define clear performance goals
- Use realistic load patterns
- Include think time between requests
- Test with production-like data
- Monitor system resources
Load Patterns
- Ramp-up gradually
- Test at sustained load
- Include spike scenarios
- Test soak/endurance
- Validate under stress
- Test auto-scaling
Metrics & Analysis
- Define SLAs upfront
- Monitor response times (p50, p95, p99)
- Track error rates
- Measure throughput
- Monitor resource utilization
- Analyze bottlenecks
Environment
- Use dedicated test environment
- Match production configuration
- Isolate test traffic
- Monitor database performance
- Test with CDN if applicable
- Include third-party dependencies
Anti-Patterns
Common Mistakes
- Testing from single location only
- Not ramping up load gradually
- Ignoring think time
- Testing without monitoring
- No baseline for comparison
- Testing in production
Test Design Issues
- Unrealistic load patterns
- Missing data variation
- No error handling
- Hard-coded test data
- Ignoring cache effects
- Not testing edge cases
What ships with it
1 file 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.
- yesterday First seen · 168 lines · 75 tokens per session scan A 6340236a43dd
load-testing-expert is a skill published in the GitHub repository personamanagmentlayer/pcl (41 stars, last pushed yesterday), licensed Apache-2.0. It adds 75 tokens to every session and 1,096 once invoked, about $0.0004 per session on Opus 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-05.
Other skills, from other repositories
performance-testing
Test application performance, scalability, and resilience. Use when planning load testing, stress testing, or optimizing system performance.
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.
load-testing-commerce
Simulate realistic shopper traffic on your checkout and catalog pages using k6 or Artillery to find performance bottlenecks before launch.
performance-tester
Design and run performance tests to identify bottlenecks, validate SLOs, and measure system capacity. Covers load tests, stress tests, and spike tests.
gatling-best-practices
Guides developers and testers in writing, fixing, and structuring Gatling load test scenarios. Use this skill whenever the user mentions load testing, performance testing, stress testing, Gatling, virtual users, VUs, ramp-up, injection profiles, simulations, JMeter migration, k6 migration, throughput, response time…
k6-best-practices
Guides developers and testers in writing, fixing, and structuring k6 load test scripts using JavaScript or TypeScript. Use this skill whenever the user mentions k6, Grafana k6, load testing with JavaScript, virtual users, VUs, scenarios, executors, thresholds, checks, SharedArray, ramp-up stages, arrival rate…