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-neoload-migrationgit 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-neoload-migration)<a href="https://agentmods.dev/skills/octoperf/octoperf-claude-plugins/octoperf-neoload-migration"><img src="https://agentmods.dev/badge/skills/octoperf/octoperf-claude-plugins/octoperf-neoload-migration/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-neoload-migration"><img src="https://agentmods.dev/badge/skills/octoperf/octoperf-claude-plugins/octoperf-neoload-migration.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.00133 | $0.14078 |
| Opus 5 | $0.00067 | $0.07039 |
| Sonnet 5 | $0.00027 | $0.02816 |
| Haiku 4.5 | $0.00013 | $0.01408 |
Grade A, and why
octoperf-neoload-migration 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 — 1,151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OctoPerf — NeoLoad migration
import_neoload_virtual_user does the mechanical part: it rebuilds the
Virtual Users, HTTP servers, variables, data files and scenarios. It
deliberately stops short of what has no OctoPerf equivalent, and hands
back everything it left undone in the response's unconverted list —
usually as a named marker planted in the tree. This skill is what
turns that list into a test that runs.
Work in this order. Skipping the first step is how migrations get committed to and then abandoned.
1. Decide before you import
Call analyze_neoload_project and read portability before anything
else:
| Verdict | What it means | What to do |
|---|---|---|
MECHANICAL |
Plain HTTP throughout | Import; expect it to run nearly as-is |
ASSISTED |
HTTP plus scripts or control flow | Import, then work the unconverted list |
MOSTLY_MANUAL |
Protocol plugins outnumber HTTP requests | Say so before importing |
MOSTLY_MANUAL is not a difficulty rating, it is a different project.
A NeoLoad plugin request (Oracle Forms, AMF, GWT, Siebel, RTMP,
Hessian) carries a proprietary dialog encoded in base64, not an HTTP
body — there is nothing to translate, and no tool on either side can
invent it. The traffic has to be recorded again against the live
application. Tell the user the count from plugins and let them decide;
importing first and discovering it later wastes their time and yours.
The per-user virtualUsers breakdown matters just as much: a project
can be MOSTLY_MANUAL overall while three of its ten users are pure
HTTP. Migrate those, and leave the rest.
A verdict of MOSTLY_MANUAL on a Virtual User with no requests at
all is an Advanced Action, not a protocol plugin: those weigh in the
verdict too, because an APM connector or a Selenium launcher converts no
better than an AMF dialog does. customActions on the breakdown says how
many.
Then read unconverted, which the assessment carries as well. Nothing has
been planted anywhere at this point, so the marker of every entry is
empty and the facts are what identify the element.
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 · 1,151 lines · 133 tokens per session scan A c325777adbda
octoperf-neoload-migration is a skill published in the GitHub repository OctoPerf/octoperf-claude-plugins (0 stars, last pushed 4d ago), licensed Apache-2.0. It adds 133 tokens to every session and 14,078 once invoked, about $0.0007 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-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.