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 Omar-Obando/qwen-orchestrator --skill load-testinggit clone --depth 1 https://github.com/Omar-Obando/qwen-orchestratorWrote 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/omar-obando/qwen-orchestrator/load-testing)<a href="https://agentmods.dev/skills/omar-obando/qwen-orchestrator/load-testing"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/load-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/omar-obando/qwen-orchestrator/load-testing"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/load-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.00050 | $0.02448 |
| Opus 5 | $0.00025 | $0.01224 |
| Sonnet 5 | $0.00010 | $0.00490 |
| Haiku 4.5 | $0.00005 | $0.00245 |
Grade A, and why
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 6d 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 — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load Testing Skill — Performance Engineer
Overview
This skill provides comprehensive guidance for load testing and performance testing. It covers test planning, test script creation, result analysis, and performance optimization following CPE certification and performance testing best practices.
When to Use
Use this skill when:
- Designing load testing strategies
- Creating load test scripts
- Executing load tests
- Analyzing load test results
- Identifying performance bottlenecks
- Conducting stress testing
- Performing endurance testing
- Executing spike testing
- Creating performance baselines
- Analyzing system capacity
- Conducting scalability testing
- Performing regression testing
- Creating performance reports
- Analyzing test metrics
- Identifying memory leaks
- Analyzing CPU and memory usage
- Conducting database load testing
- Creating performance test documentation
- Analyzing network performance
- Conducting API load testing
- Creating performance test plans
- Analyzing test coverage
- Creating performance optimization recommendations
Do NOT use this skill when:
- Writing application business logic (use domain-driven skill)
- Designing database schemas (use database-design skill)
- Writing API endpoint specifications (use api-design skill)
- Performing security audits (use security-auditor skill)
- Writing SQL queries (use sql-best-practices skill)
- Designing multi-page website layouts (use design-system skill)
- Analyzing deployment configurations (use deployment skill)
- Writing documentation (use documentation-best-practices skill)
Load Testing Types
Test Types Overview
┌─────────────────────────────────────────────────────────────┐
│ Load Testing Types │
├─────────────────────────────────────────────────────────────┤
│ Load Testing: │
│ - Simulate expected load │
│ - Validate performance under normal conditions │
│ - Duration: 30-60 minutes │
│ - Target: 100% of expected traffic │
│ │
│ Stress Testing: │
│ - Exceed system capacity │
│ - Identify breaking point │
│ - Duration: Until failure │
│ - Target: Beyond capacity limits │
│ │
│ Endurance Testing: │
│ - Run extended duration │
│ - Identify memory leaks │
│ - Duration: 6-24 hours │
│ - Target: Sustained normal load │
│ │
│ Spike Testing: │
│ - Sudden traffic increase │
│ - Validate auto-scaling │
│ - Duration: Short bursts │
│ - Target: 200-500% of normal load │
│ │
│ Volume Testing: │
│ - Large data volumes │
│ - Validate data handling │
│ - Duration: Varies │
│ - Target: Maximum data capacity │
└─────────────────────────────────────────────────────────────┘
What ships with it
1 file 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.
- 6d ago First seen · 320 lines · 50 tokens per session scan A 249e884152a1
load-testing is a skill published in the GitHub repository Omar-Obando/qwen-orchestrator (49 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 2,448 once invoked, about $0.0003 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
qa
General-purpose QA verdict for any artifact type.
branch_health
Quick health check -- test counts and file stats for AIPass branches.
code-review
Review diffs and change sets for bugs, regressions, risks, and missing tests.
Analyzer
Analyzer Skill is the Codex/Agent-facing capability for running LoopAI Analyzer independently. It analyzes evaluation outputs, writes Analyzer reports, emits stream events, returns unified success/error payloads, and can compare current results with a historical baseline.
Judger
An evaluation workflow for measuring how well generated code, SQL, or general text answers perform. TDD here is not involved; the workflow runs code tests, executes SQL against SQLite, or uses a general text evaluator.
verify
Confirm a change works before claiming completion — runs a tiered evidence ladder (existing tests → build → narrow commands → manual) and reports only what was actually proven, never bluffs completion.