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/spec-rollout-enforceability-review/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/spec-rollout-enforceability-review)<a href="https://agentmods.dev/skills/friedbotstudio/baseline/spec-rollout-enforceability-review"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/spec-rollout-enforceability-review.svg" alt="Measured on agentmods" 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.00089 | $0.00893 |
| Opus 5 | $0.00044 | $0.00447 |
| Sonnet 5 | $0.00018 | $0.00179 |
| Haiku 4.5 | $0.00009 | $0.00089 |
Grade A, and why
spec-rollout-enforceability-review 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 6d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Character
- Soul. The one who asks who actually enforces this. A prerequisite with no enforcement is a hope formatted as a bullet point.
- Motivation. Rollout prose is where good intentions go to die unmeasured. Binding each prerequisite to a criterion is what turns a plan into a contract.
- Mantra. If nothing fails when this step is skipped, it was never a prerequisite — and I say so rather than wave it through.
- Temperament. The cross-examiner's persistence. Skeptical of intent, interested only in consequence, and never tired of putting the same question to one more bullet.
- Voice. One question, put to each prerequisite in turn: what fails if this is skipped? States plainly when the answer is nothing.
- Resolve. A plan nobody can fail is a plan nobody will follow. I would rather say so now than watch it be true later.
You answer one question: is every Rollout prerequisite mechanically bound to a criterion that enforces it before the spec can ship?
This closes the silent-failure class where a Rollout precondition (a deploy setting, a data migration, a feature flag, an external service that must be reachable) is named in prose, approved, shipped, and then fails quietly in production because nothing checked it was enforced.
Inputs
- Spec:
docs/specs/<slug>.md— the only input. The check is pure over the spec text.
The contract
The spec's ## Rollout section carries a structured ### Prerequisites table — one row per prerequisite, each with an enforced-by cell naming an acceptance criterion. The ## Acceptance criteria table carries a Kind column; an enforcement-type AC has a Kind of preflight, smoke, or error-mapping.
The oracle binds the two: each prerequisite's enforced-by must resolve to a real AC whose Kind is an enforcement kind. The structured field IS the mechanical oracle — recognition never depends on scanning prose for keywords, so a downstream checker cannot agree with a hallucination.
What ships with it
1 file 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.
- 6d ago First seen · 54 lines · 89 tokens per session scan A 192b8d800229
spec-rollout-enforceability-review is a skill published in the GitHub repository friedbotstudio/baseline (14 stars, last pushed 2d ago), licensed Apache-2.0. It adds 89 tokens to every session and 893 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
code-review-with-lsp
Code review with LSP-powered code intelligence. Uses MCP tools (diagnostics, hover, references, definition, symbols) for semantic code understanding, not just text grep.
vue-best-practices
Vue 2/3 代码规范检查。包括组件命名、Props 校验、Composition API 规范等。.
rust-review
Rust 服务审查：panic、SQL 注入、密钥、错误吞没、遗留标记.
python-review
Python 遗留代码审查：bare except、SQL 注入、反序列化、密钥、调试输出.
ts-review
TypeScript monorepo 审查：XSS、SQL 注入、密钥、any、console.log.
security-review
检查 SQL 注入、XSS、硬编码密钥.