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 jaktestowac/awesome-copilot-for-testers --skill testing-performance-and-loadgit clone --depth 1 https://github.com/jaktestowac/awesome-copilot-for-testersWrote 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/jaktestowac/awesome-copilot-for-testers/testing-performance-and-load)<a href="https://agentmods.dev/skills/jaktestowac/awesome-copilot-for-testers/testing-performance-and-load"><img src="https://agentmods.dev/badge/skills/jaktestowac/awesome-copilot-for-testers/testing-performance-and-load/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/skills/jaktestowac/awesome-copilot-for-testers/testing-performance-and-load"><img src="https://agentmods.dev/badge/skills/jaktestowac/awesome-copilot-for-testers/testing-performance-and-load.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00091 | $0.02500 |
| Opus 5 | $0.00046 | $0.01250 |
| Sonnet 5 | $0.00018 | $0.00500 |
| Haiku 4.5 | $0.00009 | $0.00250 |
Grade A, and why
testing-performance-and-load 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Performance and Load
Use this skill when a system's speed or capacity is in question and the answer needs to be a number someone can act on.
Most performance testing produces numbers nobody uses. The two causes are always the same: a workload that does not resemble reality, and a result reported as an average. A test that hammers one endpoint with a flat 500 virtual users tells you how the system responds to something that will never happen, and a mean response time of 200ms is compatible with one user in twenty waiting four seconds.
When to Use
- a feature has a stated latency or throughput requirement
- "the app feels slow" needs to become a measurement
- a launch, campaign, or migration needs a capacity check
- a performance regression is suspected between two releases
- a performance result exists and needs interpreting
- a CI check should catch obvious regressions before they ship
Operating Principles
- Model the workload before writing the script. Test shape comes from real traffic: which endpoints, in what ratio, with what think time, at what concurrency.
- Percentiles, never averages. Report p50, p95, p99. The mean describes nobody's experience and hides the tail entirely.
- A threshold without an SLO is a guess. Derive the number from what users need or what the business promised, and say which.
- One variable per run. Comparing two runs that differ in load, data volume, and code changes tells you nothing about any of them.
- Environment differences invalidate the number, not just weaken it. A result from a quarter-size environment is a shape, not a capacity.
- Find the bottleneck, do not just report the symptom. "p95 is 3 seconds" is an observation; "p95 is 3 seconds because the product query has no index on
category_id" is a finding.
Workflow
Phase 0: Name the question
Different questions need different tests. Pick one per run.
| Question | Test type | Shape |
|---|---|---|
| Is it fast enough under normal load? | Load test | Steady state at expected concurrency |
| Where does it break? | Stress test | Ramp until failure |
| Does it survive a sudden surge? | Spike test | Step change up, then down |
| Does it degrade over hours? | Soak test | Steady load for 4 to 24 hours |
| Did this release make it slower? | Regression comparison | Identical shape, two builds |
| How much capacity do we have? | Capacity test | Ramp to the SLO breach point |
What ships with it
4 files 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.
- 7d ago First seen · 181 lines · 91 tokens per session scan A cb89df42055c
testing-performance-and-load is a skill published in the GitHub repository jaktestowac/awesome-copilot-for-testers (113 stars, last pushed 15d ago), licensed MIT. It adds 91 tokens to every session and 2,500 once invoked, about $0.0005 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-03.
Other skills, from other repositories
fix-tests
Focus on all unit + command tests (pytest --exclude tests/integration). Make sure they pass and fix errors. If you run into anything very odd: stop, and let me know. Mutate test code first and let me know if you think you should update application code.
character-animation-qa
Review local character animation with schema checks, Playwright browser previews, frame sampling, and FFmpeg/ffprobe final output checks.
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
nunit
Write, run, or repair .NET tests that use NUnit. Use when a repo uses NUnit, [Test], [TestCase], [TestFixture], or NUnit3TestAdapter for VSTest or Microsoft.Testing.Platform execution. USE FOR: writing or reviewing NUnit tests; using [Test], [TestCase], [TestFixture], [SetUp], [TearDown] attributes; configuring…
crap-score
Calculates CRAP (Change Risk Anti-Patterns) for a named .NET method, class, or file. USE FOR: explicit CRAP calculation or coverage-and-complexity risk within that named target, including which tests to prioritize. DO NOT USE FOR: project-wide coverage/CRAP, plateaus, or project-wide blockers/priorities…
michel-create-packmind-dataset
Seed a local Packmind instance with a realistic dataset — one organization populated with standards, commands, and skills — so an autonomous agent can exercise its own changes against lifelike data instead of an empty app. Use this whenever you need populated Packmind data to verify a change end-to-end: reproducing a…