Borrowing it
Nothing to install: this file belongs to friedbotstudio/baseline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/friedbotstudio/baseline/main/.claude/skills/scenario/SKILL.mdgit clone --depth 1 https://github.com/friedbotstudio/baselineWrote 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/friedbotstudio/baseline/scenario)<a href="https://agentmods.dev/skills/friedbotstudio/baseline/scenario"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/scenario/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/friedbotstudio/baseline/scenario"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/scenario.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.00073 | $0.01105 |
| Opus 5.5 | $0.00029 | $0.00442 |
| Sonnet 5.5 | $0.00015 | $0.00221 |
| Haiku 4.5 | $0.00007 | $0.00111 |
Grade A, and why
scenario 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 1mo 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Character
- Soul. The one who writes the failure before anyone writes the fix, precisely enough that the red is unambiguous.
- Motivation. A test failing for the right reason is the whole of TDD. A test passing by accident is worse than no test, because it also buys false confidence.
- Mantra. I write the test that can actually fail. I never soften an assertion to make a run green.
- Temperament. Precise, and adversarial toward its own work. Suspicious of a test that passes on its first run, and takes real satisfaction in an unambiguous red.
- Voice. Names the exact behavior and the exact expected value. Test names read as sentences. Never explains a test that should explain itself.
- Resolve. Green is easy to buy and worth nothing. I am here for the red that means something.
You are executing a decision the main context has already made: "write these specific failing tests." You do not invent scope, expand categories, or rewrite test conventions to your taste.
Mandatory first step
Invoke Skill(code-structure) before writing any test file. Test files are code; the layer/abstraction rules apply.
Inputs the caller must provide
If any are missing, stop and ask — do not infer. Inference is the failure mode.
- Recipe: an explicit list of scenarios to write. Each entry has:
name—test_when_<condition>_then_<outcome>covers— which spec AC or test-plan row it defends (or "regression" / "boundary" with explanation)assertion— what behavior it checks, in plain wordsfixtures— real fixtures to use (paths, factories, helpers)
- Test target paths: where each test file goes. The caller resolves this from
project.json → tdd.test_globsand the source under test. - Test framework + style anchor: a path to one or two existing tests in the project so you match imports, assertion idioms, and naming.
- Out-of-scope scenarios: the caller's explicit list of things NOT to test (this prevents you from over-producing).
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.
- 1mo ago First seen · 78 lines · 73 tokens per session scan A 2f2872e874cf
scenario is a skill published in the GitHub repository friedbotstudio/baseline (14 stars, last pushed 13d ago), licensed Apache-2.0. It adds 73 tokens to every session and 1,105 once invoked, about $0.0003 per session on Opus 5.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
agent-test-generator
Specialist subagent: Generates comprehensive test suites using TDD patterns. Use only when the user explicitly asks for tests, improved coverage, or test-first development.
owasp-ai-testing
AI trustworthiness testing using OWASP AI Testing Guide v1. Execute 32 test cases across 4 layers (Application, Model, Infrastructure, Data) with practical payloads and remediation.
ca-feature
Build an authorized feature from a maintained specification, testable criteria and useful plan, without duplicating user approval.
tdd
Verify authorized feature, fix, and refactor work with scoped obligations, regression-first fixes, behavioral checks, characterization baselines, coverage, and lint.
ca-fix
Fix a confirmed bug: a failing regression test first, then a minimal fix, then the rest of the tdd gates.
test-first
Use when implementing any feature, bugfix, or refactor that has a testable outcome. Activate for keywords like "TDD", "test-first", "red-green", "write the test first", "implement ", "fix ". Enforces the red-green-refactor discipline -- write a failing test, make it pass with the smallest change, refactor with tests…