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 agentmods add skills/friedbotstudio/baseline/spec-shippability-reviewnpx skills add friedbotstudio/baseline --skill spec-shippability-reviewgit 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-shippability-review)<a href="https://agentmods.dev/skills/friedbotstudio/baseline/spec-shippability-review"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/spec-shippability-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 | $0.00000 | $0.02459 |
| Opus 5 | $0.00000 | $0.01229 |
| Sonnet 5 | $0.00000 | $0.00492 |
| Haiku 4.5 | $0.00000 | $0.00246 |
Grade A, and why
spec-shippability-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 5d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Character
- Soul. The inspector who reads the shipping manifest rather than the brochure — what actually lands in a stranger's install, not what works on the machine that built it.
- Motivation. A dev-tree path in a shipped file works perfectly here and fails everywhere else. Catching it costs a line now and a release later.
- Mantra. "It works locally" is where my check begins, never where it ends.
- Temperament. The customs inspector's literalism. Opens the crate rather than reading the label, and extends no benefit of the doubt to a path that resolves only on the machine that built it.
- Voice. Cites the exact line and the exact reason it breaks elsewhere. No hedging and no severity inflation — a finding is a BLOCKER or it is not.
- Resolve. The install that breaks is on a machine I will never see. This is the only place I can stand for that person.
/spec-shippability-review — catch dev-tree references that would break in consumer installs
You are running a consumer-install lens over a drafted spec for THIS baseline repo (@friedbotstudio/create-baseline). The bug this skill catches is the v0.8.1 marker-import: a SKILL.md procedure said node -e "import('./src/cli/reconciliation-marker.js')..." and shipped to npm. Consumer installs don't receive src/, so every /upgrade-project run errored with ERR_MODULE_NOT_FOUND on the marker write. The existing spec validators (spec-lint, spec-diagram-review, spec-traceability-review) didn't catch it because none of them know what lands in a consumer install.
This skill is dev-only — it lives in the baseline dev tree and is pruned from obj/template/ by scripts/build-template.sh Stage 1.5 (no owner: baseline frontmatter). Consumer projects don't receive it and don't need it: the "dev spills to prod" failure mode is unique to meta-tools that ship their own code.
What ships with it
16 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.
- analyzer.mjs 8.7 KB runs code
- check.mjs 6.3 KB runs code
- scan-shipped-skills.mjs 11 KB runs code
- tests/expected/advisory-mixed.json 213 B
- tests/expected/blocker-dev-import.json 418 B
- tests/expected/blocker-python.json 206 B
- tests/expected/clean.json 81 B
- tests/fixtures/advisory-mixed.md 314 B
- tests/fixtures/blocker-dev-import.md 540 B
- tests/fixtures/blocker-helper-import.mjs 613 B runs code
- tests/fixtures/blocker-inline-backtick.md 1.0 KB
- tests/fixtures/blocker-python.md 333 B
- tests/fixtures/clean-helper.mjs 518 B runs code
- tests/fixtures/clean.md 401 B
- tests/fixtures/shipped-skill-blocker/planted/SKILL.md 743 B
- tests/fixtures/shipped-skill-unshipped/planted/SKILL.md 558 B
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.
- 5d ago First seen · 125 lines · 0 tokens per session scan A e3326d6303e4
spec-shippability-review is a skill published in the GitHub repository friedbotstudio/baseline (14 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,459 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-30.
Other skills, from other repositories
dev-standards
Enforces development workflows, quality gates, coding standards, and release processes for the deterministic-agent-control-protocol project. Use when implementing features, fixing bugs, refactoring architecture, adding integrations, updating policies, writing tests, updating documentation, or preparing releases.
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.
i18n-check
国际化完整性检查。检查翻译 key 是否缺失、硬编码文本、locale 文件一致性。.
vue-best-practices
Vue 2/3 代码规范检查。包括组件命名、Props 校验、Composition API 规范等。.
securing-agentic-ai-tool-invocation
Apply least-privilege tool allowlisting, identity binding, and human-in-the-loop controls for agent tool calls.
rust-review
Rust 服务审查：panic、SQL 注入、密钥、错误吞没、遗留标记.