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 dungnotnull/hybrid-harness-chaos-process-prm --skill s13-performance-testinggit clone --depth 1 https://github.com/dungnotnull/hybrid-harness-chaos-process-prmWrote 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/dungnotnull/hybrid-harness-chaos-process-prm/s13-performance-testing)<a href="https://agentmods.dev/skills/dungnotnull/hybrid-harness-chaos-process-prm/s13-performance-testing"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s13-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/dungnotnull/hybrid-harness-chaos-process-prm/s13-performance-testing"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s13-performance-testing.svg" alt="Reviewed on agentmods" width="80" 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.00106 | $0.04105 |
| Opus 5 | $0.00053 | $0.02053 |
| Sonnet 5 | $0.00021 | $0.00821 |
| Haiku 4.5 | $0.00011 | $0.00411 |
Grade A, and why
performance-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 11d 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 — 501 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance & Load Testing (s13)
Purpose
Establish quantitative performance baselines and validate system capacity before chaos experiments. Without knowing how the system performs under normal load, chaos results are meaningless — you can't determine if a latency spike is from the fault or from pre-existing performance issues.
Prerequisites
- Service endpoints identified and accessible
- SLAs and performance requirements defined (from s01 PRD)
- k6 installed or available as container image
- Target environment provisioned and stable
- Baseline performance metrics from s12 (E2E testing) recommended
Input Contract
| Input | Source | Required |
|---|---|---|
| Deployed service endpoints | s05 (service definitions), s10 (GitOps sync) | Yes |
| Expected traffic patterns | s01 (PRD — scale/throughput requirements) | Yes |
| Performance SLAs (p99, error rate, throughput) | s01 (NFRs), s19 (SLO targets) | Yes |
| Security scan passed | s11 (security gate verdict) | Yes |
| Load test tool preference | s02 taste (testing/tooling) | No |
| Infrastructure topology (replicas, resources) | s05 (service defs) | Yes |
Output Contract
| Output | Destination | Format |
|---|---|---|
| Performance baseline report | .commandcode/artifacts/perf/perf-baseline-<service>.json |
JSON |
| Load test scripts (k6/Locust) | .commandcode/artifacts/perf/load-test-<service>.js |
JavaScript/Python |
| Stress test results (breaking point) | .commandcode/artifacts/perf/stress-test-results.json |
JSON |
| Capacity recommendations | s23 (cloud cost), s24 (scoring) | Markdown |
| Performance SLO validation | s19 (CV config threshold tuning) | YAML |
| Baseline for chaos comparison | s14-s21 (all chaos skills) | JSON |
Load Testing Strategy
LEVEL 1: Smoke Test — 1 VU, 1 minute → Verify test scripts work
LEVEL 2: Baseline — Expected load, 5 min → Establish "normal" performance
LEVEL 3: Load Test — Peak load, 15 min → Validate production capacity
LEVEL 4: Stress Test — Ramp to breaking point → Find system limits
LEVEL 5: Soak Test — 80% peak, 1-4 hours → Memory leaks, connection leaks
LEVEL 6: Spike Test — Sudden 5x traffic burst → Autoscaling response
LEVEL 7: Chaos-Load Combined — Load + fault injection → Resilience under traffic
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.
- 11d ago First seen · 501 lines · 106 tokens per session scan A b376dabebbb4
performance-load-testing is a skill published in the GitHub repository dungnotnull/hybrid-harness-chaos-process-prm (19 stars, last pushed 3mo ago), licensed MIT. It adds 106 tokens to every session and 4,105 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-08-30.
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.
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".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
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.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.