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 commands/shinpr/nautilus/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/commands/shinpr/nautilus/recipe-vision)<a href="https://agentmods.dev/commands/shinpr/nautilus/recipe-vision"><img src="https://agentmods.dev/badge/commands/shinpr/nautilus/recipe-vision.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.00015 | $0.00044 |
| Opus 5 | $0.00008 | $0.00022 |
| Sonnet 5 | $0.00003 | $0.00009 |
| Haiku 4.5 | $0.00002 | $0.00004 |
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 yesterday.
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.
What it actually says
Load the recipe-vision skill, then follow its instructions using the request below as input.
$ARGUMENTS
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.
- yesterday First seen · 8 lines · 15 tokens per session scan A 75e03b56cbba
recipe-vision is a command published in the GitHub repository shinpr/nautilus (4 stars, last pushed 5d ago), licensed MIT. It adds 15 tokens to every session and 44 once invoked, about $0.0001 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-09-05.
Other commands, from other repositories
screens
Structures product UX screen design — inventory, flow, states, and reusable briefs for external design tools — without generating pixels or UI code.
design
Focused design session for improving video scene visuals using the frontend-design skill.
workflow-foundation-to-design
Run the end-to-end Foundation Sprint + Design Sprint workflow with narrative handoff.
incident
Coordinates the live response to an active production incident — timeline, status, and resolution — then hands off to /renata:retro for the post-mortem.
landscape
Post-PRD competitive research — maps similar solutions (anchored on the PRD), then co-curates the result with you to surface differentiation gaps that become candidate features. Sources mandatory.
phase-roadmap
Distributes all system features into sequential, time-boxed phases, with Phase 0 as the end-to-end anchor set.