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 jnPiyush/AgentX --skill performance-testinggit clone --depth 1 https://github.com/jnPiyush/AgentXWrote 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/jnpiyush/agentx/performance-testing)<a href="https://agentmods.dev/skills/jnpiyush/agentx/performance-testing"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/performance-testing/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/jnpiyush/agentx/performance-testing"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/performance-testing.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.00039 | $0.02984 |
| Opus 5.5 | $0.00016 | $0.01194 |
| Sonnet 5.5 | $0.00008 | $0.00597 |
| Haiku 4.5 | $0.00004 | $0.00298 |
Grade A, and why
performance-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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Testing
Purpose: Validate system performance, scalability, and reliability under expected and peak loads. Scope: Load testing, stress testing, spike testing, soak testing, latency benchmarking, capacity planning.
When to Use This Skill
- Establishing performance baselines before release
- Validating SLA compliance (latency, throughput, error rate)
- Capacity planning for expected traffic growth
- Identifying bottlenecks in APIs, databases, or infrastructure
- Testing autoscaling behavior under load
- Regression testing after performance-sensitive changes
- Pre-production load validation
When NOT to Use
- Functional correctness testing (use integration/e2e testing)
- Security vulnerability scanning (use security testing)
- Unit-level profiling (use language profiler directly)
Prerequisites
- Defined SLA targets (P50, P95, P99 latency, throughput, error rate)
- Representative test environment (production-like)
- Monitoring stack available (metrics, logs, traces)
- Test data that reflects production volume
Decision Tree
Performance test type?
+- How fast under normal load? -> Load Test
| +- Sustained traffic at expected concurrency
| +- Duration: 5-15 minutes
| +- Key metric: P95 latency
+- What's the breaking point? -> Stress Test
| +- Ramp beyond capacity until failure
| +- Duration: ramp until degradation
| +- Key metric: max throughput before errors
+- Can it handle sudden spikes? -> Spike Test
| +- Sudden burst of traffic
| +- Duration: brief spike + recovery
| +- Key metric: recovery time
+- Is it stable over time? -> Soak Test
| +- Moderate load for extended period
| +- Duration: 1-4 hours
| +- Key metric: memory leaks, connection leaks
+- How many users can it support? -> Capacity Test
| +- Incremental load increase
| +- Duration: stepped ramp
| +- Key metric: users at SLA threshold
Tool Selection
| Tool | Language | Best For | Cloud Option |
|---|---|---|---|
| k6 | JavaScript | Developer-friendly, CI-native | Grafana Cloud k6 |
| Locust | Python | Python teams, distributed | Azure Load Testing |
| JMeter | Java/XML | Complex scenarios, GUI | Azure Load Testing |
| Artillery | YAML/JS | Quick API tests | Artillery Cloud |
| Gatling | Scala/Java | High throughput, detailed reports | Gatling Enterprise |
| vegeta | Go | HTTP benchmarking, CLI | - |
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 · 360 lines · 39 tokens per session scan A bbb0d23df4df
performance-testing is a skill published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 39 tokens to every session and 2,984 once invoked, about $0.0002 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
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.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
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".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.