octoperf-sla

octoperf-sla is a skill for Claude Code from OctoPerf/octoperf-claude-plugins. It costs 0 tokens per session (2,027 once invoked), scanned A, original, Apache-2.0.

A guide for defining pass and fail thresholds for OctoPerf load tests. These thresholds specify limits such as how slow a simulated user's requests may be or how many errors are acceptable.

In plain words
What is it for?
Use it to create and attach SLA profiles to simulated users, such as requiring checkout requests to stay under a chosen time.
Why use it?
It replaces subjective report-checking with explicit rules that show whether a test met its performance targets.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the octoperf plugin — 20 skills, 1 MCP server shipped together

Good fit Use it to create and attach SLA profiles to simulated users, such as requiring checkout requests to stay under a chosen time.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/octoperf/octoperf-claude-plugins/octoperf-sla
Install

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.

Any agent
npx skills add OctoPerf/octoperf-claude-plugins --skill octoperf-sla
Clone the repo
git clone --depth 1 https://github.com/OctoPerf/octoperf-claude-plugins

Made for: Claude Code.

Or install octoperf, the plugin that ships this one along with the rest of its 20 skills, 1 MCP server.

Wrote 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.

agentmods badge for octoperf-sla

README.md
[![agentmods](https://agentmods.dev/badge/skills/octoperf/octoperf-claude-plugins/octoperf-sla/github.svg)](https://agentmods.dev/skills/octoperf/octoperf-claude-plugins/octoperf-sla)
Your own site
<a href="https://agentmods.dev/skills/octoperf/octoperf-claude-plugins/octoperf-sla"><img src="https://agentmods.dev/badge/skills/octoperf/octoperf-claude-plugins/octoperf-sla/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.

agentmods 80×15 button for octoperf-sla

Your own site · 80×15
<a href="https://agentmods.dev/skills/octoperf/octoperf-claude-plugins/octoperf-sla"><img src="https://agentmods.dev/badge/skills/octoperf/octoperf-claude-plugins/octoperf-sla.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,027 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02027
Opus 5 $0.00000 $0.01014
Sonnet 5 $0.00000 $0.00405
Haiku 4.5 $0.00000 $0.00203

Measured 12d ago against content hash 169cea3bb8db, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

octoperf-sla 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.

plugins/octoperf/skills/octoperf-sla/SKILL.md · 167 lines

How it starts

The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design SLA profiles — pass/fail bands on a test's own metrics

Define what "too slow" and "too many errors" mean for a Virtual User, so a run raises alarms instead of leaving someone to eyeball the report. Read this before creating or editing an SLA profile.

Two different things are called SLA

Get this right first — the tools do not overlap.

Design SLA profile (this skill) SLA monitor (create_sla_monitor)
Scope attached to a Virtual User created on a project
Metrics the ones you pick, with your bands a fixed default set of per-request counters
Set up create_sla_profileattach_sla_profile_to_virtual_user one call, pick an UP agent
Use it when you have a target to enforce ("checkout under 1s") you want per-request SLA counters with no thinking

They can coexist on the same project. create_sla_monitor is documented in octoperf://skills/monitoring; everything below is about profiles.

Both show up under Pass Criteria on the scenario page, next to the thresholds of the project's other monitors — what a passed run means, in one place. octoperf://skills/scenario-composition says what that step covers and how to read the criteria a test already has.

Mental model

A profile is a named set of threshold groups. One group = one metric plus the graded bands that fire on it:

SLAProfile "Checkout SLA"
└── SLAMonitorThreshold  metric = RESPONSE_TIME_AVG
    ├── Threshold  WARNING   value > 1000 ms   for 10 samples
    └── Threshold  CRITICAL  value > 3000 ms   for 3 samples

A band carries three things:

  • severityPASSED, WARNING or CRITICAL. PASSED is not decoration: some metrics (Apdex, hits rate) declare the good band explicitly.
  • value — a range: lowerEndpoint / upperEndpoint with OPEN (exclusive) or CLOSED (inclusive) bound types. An omitted endpoint means unbounded{lowerEndpoint: 5, lowerBoundType: "CLOSED"} is "5 or more".
  • time — how long it must hold before firing, one of two shapes: {"@type":"OccurrenceCondition","times":10} (10 samples in a row) or {"@type":"DurationCondition","duration":30000} (milliseconds, not seconds).

Read the full file on GitHub · 167 lines

Changes

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.

  1. 12d ago First seen · 167 lines · 0 tokens per session scan A 169cea3bb8db

Subscribe to this mod's changes

octoperf-sla 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 2,027 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.

Related

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…

atlassian/forge-skills · 134 tokens

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…

hyhmrright/logic-lens · 108 tokens

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.

LichAmnesia/lich-skills · 68 tokens

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…

hyhmrright/logic-lens · 183 tokens

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.

sumup/sumup-skills · 47 tokens

python-testing

Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.

Jamkris/everything-gemini-code · 24 tokens