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-validation-triagegit 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-validation-triage)<a href="https://agentmods.dev/skills/octoperf/octoperf-claude-plugins/octoperf-validation-triage"><img src="https://agentmods.dev/badge/skills/octoperf/octoperf-claude-plugins/octoperf-validation-triage/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-validation-triage"><img src="https://agentmods.dev/badge/skills/octoperf/octoperf-claude-plugins/octoperf-validation-triage.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.00105 | $0.04232 |
| Opus 5 | $0.00053 | $0.02116 |
| Sonnet 5 | $0.00021 | $0.00846 |
| Haiku 4.5 | $0.00011 | $0.00423 |
Grade A, and why
octoperf-validation-triage 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 — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OctoPerf — Validation-failure triage
When a Virtual User validation finishes with many failing actions, reading each failure detail one by one wastes context window and time. This skill groups failures by root cause, drills into one representative per group, and maps each group to the correct fix.
When this applies
- A
validate_virtual_userrun finished withfinished=trueand at least one failing action. - The user wants to know what's wrong, not just retry blindly.
Steps
1. Get the failure index — no bodies yet
mcp__octoperf__get_virtual_user_validation_index(virtualUserId)
The index returns one entry per validated HTTP action — actionId,
success/total counts, successTimestamps and failedTimestamps. For
triage, focus on the entries whose failedTimestamps is non-empty (the
actions that failed at least one run); entries with only successTimestamps
passed every run. Do not fetch failure details yet — the index alone is
usually enough to classify.
(A successTimestamps entry is also a handle to read a passing run's
body: pass it to fetch_validation_http_body with
kind=VALIDATION_RESPONSE — e.g. to inspect what a Debug-style action
actually captured on a green run.)
OctoPerf's "KO" rule isn't just "non-2XX". A sample is KO when:
| Live response code | Recorded response code | Result |
|---|---|---|
| 2XX | none | ✅ OK |
| 2XX | 2XX | ✅ OK |
| 2XX | 3XX | ❌ KO (recording expected a redirect, got a body — usually wrong) |
| 3XX | 3XX | ✅ OK |
| 3XX | 2XX | ❌ KO (recording expected a body, got a redirect) |
| Any 4XX / 5XX | anything | ❌ KO |
| Unknown code | anything | ❌ KO |
| Any code | 4XX / 5XX / unknown | ❌ KO (recording was already broken; re-record) |
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 · 304 lines · 105 tokens per session scan A 371f704f50e6
octoperf-validation-triage is a skill published in the GitHub repository OctoPerf/octoperf-claude-plugins (0 stars, last pushed 5d ago), licensed Apache-2.0. It adds 105 tokens to every session and 4,232 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-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.