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 QAInsights/perf-skills --skill perfgit clone --depth 1 https://github.com/QAInsights/perf-skillsWrote 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/qainsights/perf-skills/perf)<a href="https://agentmods.dev/skills/qainsights/perf-skills/perf"><img src="https://agentmods.dev/badge/skills/qainsights/perf-skills/perf.svg" alt="Measured on agentmods" 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.00172 | $0.04830 |
| Opus 5 | $0.00086 | $0.02415 |
| Sonnet 5 | $0.00034 | $0.00966 |
| Haiku 4.5 | $0.00017 | $0.00483 |
Grade A, and why
perf 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 8d 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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Testing Skill
This skill provides expert, opinionated guidance across the full performance testing lifecycle - from workload design through production observation. It covers both commercial tools (LoadRunner, NeoLoad, OctoPerf) and open-source tools (JMeter, k6, Gatling, Locust).
How to Use This Skill
Read the relevant reference files based on what the user needs. Multiple files may apply.
Loading Priority Rules
- Tool-specific syntax/config → load the tool file only.
- Strategy/concepts (workload design, test data, analysis) → load the topic file only.
- Both apply (e.g., "JMeter CI/CD") → load the topic file first for patterns, then the tool file for syntax.
- Never load all files at once - select the 1–2 most relevant.
- Cross-cutting principles (assertions, think time, parameterization) → this file's Key Principles section is the single source of truth.
Reference Map
| User needs help with... | Read this file |
|---|---|
| Choosing the right tool | This file - Tool Selection Matrix (fast path) and references/topics/tool-selection.md (live perf.jmeter.ai catalog) |
| Tool alternatives, comparisons, niche/SaaS tools, licensing | references/topics/tool-selection.md |
| JMeter scripts, plugins, config | references/tools/jmeter.md |
| k6 scripting, extensions, cloud | references/tools/k6.md |
| Gatling simulations, Scala/Java DSL | references/tools/gatling.md |
| Locust Python tests, distributed | references/tools/locust.md |
| Artillery YAML/JS/TS scripts, cloud | references/tools/artillery.md |
| NeoLoad projects, GUI, APIs | references/tools/neoload.md |
| LoadRunner scripts, protocols, VuGen | references/tools/loadrunner.md |
| OctoPerf cloud test management | references/tools/octoperf.md |
| Designing workloads, concurrency, pacing | references/topics/workload-design.md |
| Test data, parameterization, CSV feeds | references/topics/test-data.md |
| Script patterns, best practices | references/topics/script-generation.md |
| Correlation, extractors, dynamic values | references/topics/correlation.md |
| CI/CD, distributed execution, cloud runners | references/topics/test-execution.md |
| Analyzing results, percentiles, SLAs | references/topics/results-analysis.md |
| APM, metrics, tracing, dashboards | references/topics/observability.md |
| Staging vs production testing strategies | references/topics/production-testing.md |
| gRPC, GraphQL, WebSocket, messaging protocols | references/topics/protocol-testing.md |
| Database load testing (JDBC, connection pools) | references/topics/database-testing.md |
| Microservices, K8s, serverless performance | references/topics/modern-architectures.md |
| LLM inference: TTFT, TPOT/ITL, TPS, goodput | references/topics/llm-inference.md |
| SLOs, error budgets, capacity & headroom | references/topics/slo-capacity.md |
What ships with it
24 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.
- evals/evals.json 11 KB
- evals/trigger-eval.json 1.8 KB
- references/tools/artillery.md 11 KB
- references/tools/gatling.md 7.7 KB
- references/tools/jmeter.md 7.6 KB
- references/tools/k6.md 7.6 KB
- references/tools/loadrunner.md 4.5 KB
- references/tools/locust.md 3.9 KB
- references/tools/neoload.md 3.3 KB
- references/tools/octoperf.md 2.0 KB
- references/topics/correlation.md 24 KB
- references/topics/database-testing.md 7.5 KB
- references/topics/llm-inference.md 11 KB
- references/topics/modern-architectures.md 11 KB
- references/topics/observability.md 6.7 KB
- references/topics/production-testing.md 7.5 KB
- references/topics/protocol-testing.md 12 KB
- references/topics/results-analysis.md 8.2 KB
- references/topics/script-generation.md 7.3 KB
- references/topics/slo-capacity.md 7.6 KB
- references/topics/test-data.md 6.2 KB
- references/topics/test-execution.md 8.6 KB
- references/topics/tool-selection.md 7.7 KB
- references/topics/workload-design.md 7.1 KB
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.
- 8d ago First seen · 360 lines · 172 tokens per session scan A 83885bddddc9
perf is a skill published in the GitHub repository QAInsights/perf-skills (15 stars, last pushed 9d ago), licensed MIT. It adds 172 tokens to every session and 4,830 once invoked, about $0.0009 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-08-30.
Other skills, from other repositories
acceptance-tester
Agents should invoke this skill as the final gate before release, handoff, or claiming completion for substantial changes. Runs acceptance/readiness checks, determines pass/fail, and gives a go/no-go recommendation.
test-plan-generator
Agents should invoke this skill when planning tests from specs, architecture docs, PRs, risky changes, new features, bug fixes, or release work. Generates prioritized unit, integration, E2E, regression, and edge-case coverage.
coding
Use when five specialized coding agents (linter, perf, refactor, security, test) that enforce quality gates across the development lifecycle. From lint enforcement through performance profiling, refactoring, security auditing, and test coverage. Use when working with coding agents.
pixi-vn-testing
Use when an AI agent (or any external script) needs to play-test a running Pixi'VN game end-to-end in a real browser — starting the game, advancing/branching the story, answering input prompts, going back, and reading/writing storage — via Game.testing, the opt-in devtools bridge exposed on window. Load this before…
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".