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 shinpr/nautilus --skill recipe-blueprintgit clone --depth 1 https://github.com/shinpr/nautilusWrote 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/shinpr/nautilus/recipe-blueprint)<a href="https://agentmods.dev/skills/shinpr/nautilus/recipe-blueprint"><img src="https://agentmods.dev/badge/skills/shinpr/nautilus/recipe-blueprint/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/shinpr/nautilus/recipe-blueprint"><img src="https://agentmods.dev/badge/skills/shinpr/nautilus/recipe-blueprint.svg" alt="Reviewed on agentmods" width="80" 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.00042 | $0.00792 |
| Opus 5 | $0.00021 | $0.00396 |
| Sonnet 5 | $0.00008 | $0.00158 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
recipe-blueprint 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context: Create or update structural design artifacts in docs/product/design/ so prototype generation and PRD authoring reuse the same design context.
Required Skills [LOAD BEFORE EXECUTION]
- [LOAD IF NOT ACTIVE]
blueprint-standards— artifact selection and templates
Conditional Skills [LOAD WHEN TRIGGERED]
- WHEN the selected artifacts define user-facing states, persona-sensitive behavior, or accessibility boundaries: [LOAD IF NOT ACTIVE]
design-perspective - WHEN the selected artifacts require state-design or product-confidence rules: [LOAD IF NOT ACTIVE]
product-principles
A blueprint may contain any subset of the defined artifacts.
Execution Decision Flow
1. Context Reading
Identify the prototype or PRD decision that needs shared design context. Read only the available vision, principles, personas, Opportunities, journeys, and learnings that can change that decision.
When missing evidence leaves the design outcome materially ambiguous, name the exact product decision required from the user. Otherwise proceed with the available evidence and mark the assumption in the affected artifact.
2. IA and Key Flow Definition
Use blueprint-standards references:
references/ia-template.mdreferences/flow-template.md
When navigation or task sequence affects the consumer, capture:
- page hierarchy
- navigation model
- labeling and taxonomy
- the critical user flows needed by the consumer, with entry, success, and relevant recovery paths
3. Content Model Definition
When entity shape or lifecycle affects the consumer, use references/content-model-template.md to define:
- core entities
- relationships
- lifecycle states when relevant
- where those entities appear in the product
4. Brand Direction and Visual Tokens
When visual consistency affects the consumer, use references/brand-direction-template.md to define:
- tone and voice
- color and typography direction
- motion and density choices
- reference products
- Visual Tokens for prototype consistency
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.
- 5d ago Changed · +2 lines 7893ad586b93
- 10d ago First seen · 89 lines · 42 tokens per session scan A a753dc979628
recipe-blueprint is a skill published in the GitHub repository shinpr/nautilus (4 stars, last pushed 9d ago), licensed MIT. It adds 42 tokens to every session and 792 once invoked, about $0.0002 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-31.
Other skills, from other repositories
blueprint-standards
Defines structural design artifact formats — information architecture, user flows, content model, brand direction, and AI interaction model. Use when creating or reviewing structural design documents that precede prototype generation.
recipe-blueprint
Define structural design foundation — information architecture, user flows, content model, brand direction, and AI interaction model — from validated opportunities and hypotheses.
design-perspective
Integrates design principles, WCAG 2.2 AA accessibility, persona context, and state design into product decisions. Use when reviewing UX decisions, checking accessibility, applying design principles, or ensuring state coverage in acceptance criteria.
prototype-guide
Generates self-contained HTML prototypes with design context from project files. Read design principles, personas, and hypothesis files, then produce a working prototype for Usability and Value risk validation. Use when creating prototypes or validating through tangible artifacts.
recipe-refine-visuals
Optional side-workflow for design experts to refine Concrete Tokens in brand-direction.md when a named downstream consumer needs reproducible values.
productspec
Use when implementing, reviewing, planning, or changing work governed by a Product Spec. Treat .product-spec.md files as the product contract for the work.