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 BlackBeltTechnology/pi-agent-dashboard --skill scenario-designgit clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboardWrote 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/blackbelttechnology/pi-agent-dashboard/scenario-design)<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/scenario-design"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/scenario-design/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/blackbelttechnology/pi-agent-dashboard/scenario-design"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/scenario-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00088 | $0.02839 |
| Opus 5 | $0.00044 | $0.01419 |
| Sonnet 5 | $0.00018 | $0.00568 |
| Haiku 4.5 | $0.00009 | $0.00284 |
Grade A, and why
scenario-design 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Turn a change spec into adversarial, real-life test scenarios — designed to break the system, not confirm it works. A scenario is only as good as it is concrete and executable. If the spec can't supply the concrete bits, that is a spec defect, surfaced as a clarification — not a guess.
Input: A change/feature spec. --change <name> (OpenSpec), or infer from
context / point the skill at any spec doc.
Mode: --stage proposal|design|apply (default: infer — see Gate).
Output: a standalone test-plan.md catalog written to your change/spec's
test-plan location (OpenSpec: openspec/changes/<name>/test-plan.md).
Core mechanism — the Triple
Every scenario MUST resolve three concrete slots:
┌─────────────┬──────────────────────┬────────────────────────────┐
│ INPUT │ TRIGGER │ EXPECTED OBSERVABLE OUTCOME │
│ concrete │ the condition / │ a measurable, visible fact │
│ data / │ action that fires │ (status, value, latency, │
│ state │ the behaviour │ DOM, log line, exit code) │
└─────────────┴──────────────────────┴────────────────────────────┘
Rule (from spec-coding edge-case practice): if any slot is a verb without a noun, or an adjective instead of a number, the slot is unfillable → spec gap. "Handles errors gracefully" is not a Triple. "POST /api/restart while server already restarting (input) → second caller (trigger) → receives 409 within 500ms, no second orchestrator spawned (observable)" is.
Stance: falsify, don't confirm. For each requirement, the job is to find the input+trigger that makes the observable wrong. Happy path is table stakes; the scenario value is in the boundaries and failures.
Phase 1 — Read the spec, classify requirements
- Read what exists (OpenSpec layout shown; in a non-OpenSpec project read
whatever spec/design/task docs the user points at — do not fail on a missing
openspec/dir or CLI):openspec/changes/<name>/proposal.md(always)openspec/changes/<name>/design.md(if present — decisions, invariants)openspec/changes/<name>/specs/**/spec.md(requirement deltas)openspec/changes/<name>/tasks.md(if present — to align section numbers)
What ships with it
2 files 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.
- 11d ago First seen · 223 lines · 88 tokens per session scan A dc18e29298f6
scenario-design is a skill published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (279 stars, last pushed today), licensed MIT. It adds 88 tokens to every session and 2,839 once invoked, about $0.0004 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-30.
Other skills, from other repositories
goga-accept-test-assessment
Cell test coverage assessment for acceptance review.
goga-accept-usage-review
Validate cell-level usage files against actual implementation during acceptance.
goga-accept-scope
Defines the acceptance scope — the set of cells for a given functionality.
goga-change-test-engineer
Test Coverage Validation and Behavioral Testing.
rn-testing
This skill should be used when the user asks to "write a Maestro test", "create E2E flows", "add testIDs", "run UI tests", "run E2E tests", "verify a feature works", "test my screen", "set up maestro-runner", "mock network requests", "inspect store state", "write test assertions", or needs guidance on test timing…
capturing-proof
This skill should be used when the user asks to "capture proof", "record a demo of this feature", "make a video showing it works", "record the flow for the PR", "generate a PR body", "capture screenshots for the PR", "proof-capture", or when a verified feature needs PR-ready proof artifacts (video + numbered…