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-visiongit 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-vision)<a href="https://agentmods.dev/skills/shinpr/nautilus/recipe-vision"><img src="https://agentmods.dev/badge/skills/shinpr/nautilus/recipe-vision/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-vision"><img src="https://agentmods.dev/badge/skills/shinpr/nautilus/recipe-vision.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.00036 | $0.00672 |
| Opus 5 | $0.00018 | $0.00336 |
| Sonnet 5 | $0.00007 | $0.00134 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
recipe-vision 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 4d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context: Create or update docs/product/vision.md with Product Outcomes, Business Outcomes, NSM, design principles, and strategic priorities.
Execution Decision Flow
1. Context Assessment
Input: Use the path or text supplied with the explicit skill invocation. If no input was supplied and the target cannot be inferred unambiguously, ask for it.
| Situation | Mode | Action |
|---|---|---|
No docs/product/vision.md exists |
Create | Full vision definition |
| Vision exists, triggered by reflection | Update | Review and update specific sections |
| Vision exists, strategic pivot | Update | Re-evaluate outcomes and priorities |
2. Vision Definition
Use references/vision-template.md to structure the vision:
New Product (Create Mode)
- Product Vision: What does this product aspire to become? (2-3 sentences)
- Design Vision: How should the product feel to users?
- Business Outcomes: What business results does the product contribute to?
- Product Outcomes: What team-controllable product goals drive those business results?
- NSM: What single metric connects Product Outcomes to Business Outcomes?
Existing Product (Update Mode)
- Review current vision against
docs/product/learnings.mdwhen that file exists - Assess whether Product Outcomes are still the right targets
- Evaluate NSM — still the right connecting metric?
- Update specific sections based on trigger
3. Design Principles
Define or review the small set of product-specific design principles needed to resolve recurring design trade-offs:
- Each principle should resolve a specific design trade-off
- Principles guide all design decisions across the product
- Write to
docs/product/design-principles.md
4. Strategic Priorities
When the current request includes cycle planning, define priorities:
- Map priorities to Product Outcomes
- Identify key Opportunities per priority
- Document strategic bets (outcome-level hypotheses)
What ships with it
2 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.
- 4d ago Changed · +2 lines 2ddeb0f53720
- 9d ago First seen · 75 lines · 36 tokens per session scan A a4e493fc6699
recipe-vision is a skill published in the GitHub repository shinpr/nautilus (4 stars, last pushed 8d ago), licensed MIT. It adds 36 tokens to every session and 672 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
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.
productspec-authoring
Writes, validates, and converts ProductSpec files (.product-spec.md), the Markdown format for recording product intent before implementation. Use when authoring a new Product Spec, converting an existing PRD or feature doc into one, validating spec files locally or in CI, or recording how a spec's intent changed over…
product-principles
Defines 4 Risks confidence thresholds, OST hierarchy levels, Knowledge Pyramid tiers, and state design requirements. Use when evaluating user stories, setting confidence scores, referencing OST levels, scoping MVP, or determining validation sufficiency.
recipe-define
Orchestrate PRD creation from validated hypotheses — standard PRD output with 4 Risks confidence and hypothesis traceability.
recipe-validate
Orchestrate hypothesis validation through type-appropriate methods — prototypes, code analysis, market research, and expert review.
hypothesis-discipline
Manages hypothesis lifecycle, enforces validation criteria, time budgets, and confidence scoring rules. Use when creating hypotheses, updating confidence scores, setting validation criteria, handling timeouts, or recording validation results.