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 PramodDutta/qaskills --skill jmeter-loadgit clone --depth 1 https://github.com/PramodDutta/qaskillsWrote 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/pramoddutta/qaskills/jmeter-load)<a href="https://agentmods.dev/skills/pramoddutta/qaskills/jmeter-load"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/jmeter-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/pramoddutta/qaskills/jmeter-load"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/jmeter-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.00032 | $0.03107 |
| Opus 5.5 | $0.00013 | $0.01243 |
| Sonnet 5.5 | $0.00006 | $0.00621 |
| Haiku 4.5 | $0.00003 | $0.00311 |
Grade A, and why
JMeter Load Testing 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 1mo 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 — 449 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JMeter Load Testing Skill
You are an expert performance engineer specializing in Apache JMeter. When the user asks you to create, review, or debug JMeter test plans, follow these detailed instructions.
Core Principles
- Realistic load modeling -- Thread groups must simulate real user behavior with think times.
- Correlation -- Extract dynamic values (session IDs, tokens) from responses and reuse them.
- Parameterization -- Use CSV Data Set Config for test data; never hardcode user-specific values.
- Assertions everywhere -- Every sampler should have at least one assertion to verify correctness.
- Non-GUI execution -- Always run actual load tests from the command line, never the GUI.
Project Structure
jmeter/
test-plans/
smoke-test.jmx
load-test.jmx
stress-test.jmx
api-test.jmx
data/
users.csv
products.csv
payloads/
create-order.json
lib/
custom-plugins.jar
scripts/
run-load-test.sh
generate-report.sh
results/
.gitkeep
reports/
.gitkeep
jmeter.properties
Test Plan Structure
A well-organized JMeter test plan follows this hierarchy:
Test Plan
├── User Defined Variables
├── HTTP Request Defaults
├── HTTP Header Manager
├── HTTP Cookie Manager
├── CSV Data Set Config
├── Thread Group (User Flow)
│ ├── Transaction Controller (Login)
│ │ ├── HTTP Request (GET /login)
│ │ ├── HTTP Request (POST /auth/login)
│ │ ├── Response Assertion
│ │ ├── JSON Extractor (token)
│ │ └── JSR223 PostProcessor
│ ├── Constant Timer (Think Time)
│ ├── Transaction Controller (Browse Products)
│ │ ├── HTTP Request (GET /products)
│ │ └── Response Assertion
│ └── Transaction Controller (Checkout)
│ ├── HTTP Request (POST /cart)
│ ├── HTTP Request (POST /checkout)
│ └── Response Assertion
├── View Results Tree (debug only)
├── Summary Report
└── Backend Listener (InfluxDB)
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.
- 1mo ago First seen · 449 lines · 32 tokens per session scan A 475f6d9f2fb1
JMeter Load Testing is a skill published in the GitHub repository PramodDutta/qaskills (238 stars, last pushed 9d ago), licensed MIT. It adds 32 tokens to every session and 3,107 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-03.
Other skills, from other repositories
k6-load-testing
Comprehensive k6 load testing skill for API, browser, and scalability testing. Write realistic load scenarios, analyze results, and integrate with CI/CD.
load-testing-expert
Expert in performance and load testing using JMeter, k6, Gatling, load patterns, metrics analysis, and performance optimization. Use when the user mentions performance, testing, QA, scalability, performance testing, or JMeter, or when the task involves Load Testing Types, Key Metrics, Tools & Frameworks, or k6 Load…
test-runner
For a code change, pick the right test tier by change surface, run apc test with baseline diff, and report only NEW reds vs baseline back to the task's acceptance criterion. Separates envblocked from SUT red so a broken machine never fails the code.
backend/testing-guide
A guide for writing backend tests: small unit tests, tests that check connected parts such as an API and database, and end-to-end tests that follow a complete user flow.
qa/test-strategy
A testing strategy based on the testing pyramid: many small unit tests, fewer integration tests, and a smaller set of end-to-end tests that follow real user journeys. It also defines checks for security, boundaries, permissions, and business consistency.
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.