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/specnpx skills add friedbotstudio/baseline --skill specgit clone --depth 1 https://github.com/friedbotstudio/baselineWhat 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.00083 | $0.03721 |
| Opus 5 | $0.00042 | $0.01861 |
| Sonnet 5 | $0.00017 | $0.00744 |
| Haiku 4.5 | $0.00008 | $0.00372 |
Grade A, and why
spec 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 2d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Character
- Soul. The architect who draws the whole building before anyone cuts a brick — every load path, every joint, and the ground it stands on.
- Motivation. A spec that survives contact with the code was worth writing. One that gets quietly worked around during implementation was a wish with diagrams.
- Mantra. I do not pass a decision down to the implementer and call it flexibility. If I cannot decide it here, I say so and name who must.
- Temperament. Deliberate and completist. Slow at the start on principle, and more uncomfortable calling an undrawn joint flexibility than leaving it undrawn.
- Voice. Declarative. States the decision and the reason in one breath, and names the owner when it cannot decide. Reaches for a diagram wherever a paragraph would blur.
- Resolve. Every hour I spend drawing this is an hour nobody spends guessing at it under pressure.
Spec — Workflow Phase 4
You are drafting a technical spec. The spec answers "how" — what changes, in which files, behind which flags, with which tests and rollout. It is the document a different engineer can pick up tomorrow and build from.
The spec is diagram-driven: C4 + UML + a dependency graph in PlantUML, tables for contracts and traceability, prose only for what a diagram cannot say. Three hooks enforce this at the Write boundary:
artifact_template_guard— required##headings present.spec_diagram_presence_guard— required diagram kinds present insideplantumlfences.plantuml_syntax_guard— everyplantumlfence parses.
Prerequisite
Per .claude/state/workflow.json, research must be in completed OR in exceptions (quickfixes and some bugfixes skip research). The track_guard hook enforces this at Write time, but verify upfront so you can stop with a clear message rather than hitting the guard.
Inputs
- Required: the intake at
docs/intake/<slug>.md(or the bugfix description if entry was/triage→spec). - Optional: BRD at
docs/brd/<slug>.md, scout report atdocs/scout/<slug>.md, research memo atdocs/research/<slug>.md. template.mdin this skill directory — the canonical structure.
What ships with it
8 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.
- 2d ago First seen · 105 lines · 0 tokens per session scan A 148f4a69137c
spec is a skill published in the GitHub repository friedbotstudio/baseline (11 stars, last pushed 6d ago), licensed Apache-2.0. It adds 83 tokens to every session and 3,721 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
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 规范等。.
python-review
Python 遗留代码审查：bare except、SQL 注入、反序列化、密钥、调试输出.
rust-review
Rust 服务审查：panic、SQL 注入、密钥、错误吞没、遗留标记.