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 OctoPerf/octoperf-claude-plugins --skill octoperf-scenario-compositiongit clone --depth 1 https://github.com/OctoPerf/octoperf-claude-pluginsWrote 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/octoperf/octoperf-claude-plugins/octoperf-scenario-composition)<a href="https://agentmods.dev/skills/octoperf/octoperf-claude-plugins/octoperf-scenario-composition"><img src="https://agentmods.dev/badge/skills/octoperf/octoperf-claude-plugins/octoperf-scenario-composition/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/octoperf/octoperf-claude-plugins/octoperf-scenario-composition"><img src="https://agentmods.dev/badge/skills/octoperf/octoperf-claude-plugins/octoperf-scenario-composition.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.00000 | $0.01897 |
| Opus 5 | $0.00000 | $0.00949 |
| Sonnet 5 | $0.00000 | $0.00379 |
| Haiku 4.5 | $0.00000 | $0.00190 |
Grade A, and why
octoperf-scenario-composition 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 12d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scenario composition — user profiles, load shapes, engines
A scenario is a list of user profiles. One profile = one Virtual User, played on
one provider location, under one load shape, through one engine. Read this before
building or reshaping one; octoperf://schema/scenario carries the exact field
list, this page carries the parts a schema cannot say — including what says the run
passed, which lives nowhere in that schema.
Create, then patch
Never hand-write a whole profile. Create the scenario with a create_scenario_*
shortcut using a VU of the engine type you want — the backend fills a complete
engine block — then change what you need with patch_scenario (RFC 6902) or
update_user_profile.
An engine block written from scratch has to get bandwidth, browser.cache,
browser.cookies, dns, jtl and properties all right, and the round-trip
validation rejects an incomplete one.
Load shapes
Four shapes, every duration in milliseconds, and the shortcut that creates each:
@type |
Fields | Shortcut |
|---|---|---|
UserProfileLoadRampUp |
delayMs, rampUpMs, plateauMs, plateauVus |
create_scenario_ramp_up |
UserProfileLoadRampUpThenRampDown |
the same + rampDownMs |
create_scenario_ramp_up_down |
UserProfileLoadAscendingStairs |
the same + stepCount |
create_scenario_stairs |
UserProfileLoadCustom |
points: a list of ThreadGroupPoint |
none — patch only |
The shortcuts take seconds and multiply; the persisted document is in
milliseconds, and the scenario's Load step draws the same shapes as a curve.
rampUpMs: 0 collapses to an instant constant load. Each shortcut applies the same
shape to every profile it creates: differentiating them is a patch.
One engine per Virtual User type
The engine block is not free-form — it follows the type of the VU the profile plays:
| VU type | Engine | Carries |
|---|---|---|
JMETER |
JmeterUserProfileEngine |
settings, bandwidth, browser, dns, jtl, properties |
WEB_DRIVER |
SeleniumUserProfileEngine |
settings, bandwidth |
PLAYWRIGHT |
PlaywrightUserProfileEngine |
settings, device, timeoutMs, baseURL, slowMoMs |
FRAGMENTS |
none | a fragment is reusable content, it cannot be loaded on its own |
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.
- 12d ago First seen · 146 lines · 0 tokens per session scan A be2d317bf5d2
octoperf-scenario-composition is a skill published in the GitHub repository OctoPerf/octoperf-claude-plugins (0 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,897 tokens. 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-31.
Other skills, from other repositories
forge-app-review
Performs a lightweight pre-release readiness review of Atlassian Forge apps across manifest/module wiring, architecture, runtime compatibility, dependency posture, tests, deploy readiness, and obvious security, cost, or reliability smells. Use when the user asks "review my Forge app", "pre-deploy check", "is this app…
run-iteration-eval
Run the Logic-Lens content-eval pipeline for one iteration and produce a scored summary.json — use to measure a skill change. Wraps scripts/run-content-evals.sh (runner, costs tokens) and scripts/grade-iteration.py (grader, free, re-runnable). ALWAYS sync the plugin cache first. Use when the user wants to "run the…
spec-driven-dev
Use when starting any non-trivial feature, refactor, or new project that will touch more than one file. Drives an AI coding agent through a gated Spec → Plan → Build → Test → Review → Ship lifecycle so work is specified before it is built, verified before it is reviewed, and reviewed before it ships.
iterate-skill
Run the Logic-Lens skill-improvement loop end to end — baseline → diagnose failures → edit → sync cache → re-eval → verify net gain → iterate until clean. Use whenever the goal is to RAISE a skill's eval score or fix a failing eval mode: "improve logic-review", "the format compliance is failing, fix it", "iterate on…
sumup-testing
Set up and run SumUp sandbox tests. Use when configuring a SumUp test merchant, picking test cards, triggering deliberate failure (amount = 11), or building a SumUp end-to-end test harness.
python-testing
Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.