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.
git 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-define)<a href="https://agentmods.dev/commands/shinpr/nautilus/recipe-define"><img src="https://agentmods.dev/badge/commands/shinpr/nautilus/recipe-define.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.00011 | $0.00040 |
| Opus 5 | $0.00005 | $0.00020 |
| Sonnet 5 | $0.00002 | $0.00008 |
| Haiku 4.5 | $0.00001 | $0.00004 |
Grade A, and why
recipe-define 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-define 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 · 11 tokens per session scan A 77789f66c4d4
recipe-define is a command published in the GitHub repository shinpr/nautilus (4 stars, last pushed 5d ago), licensed MIT. It adds 11 tokens to every session and 40 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
status
Reports where the project stands in the RENATA flow and points to the next step, gating the current step behind human verification, without running any step commands.
bug-report
Converts a raw bug report from production into a structured, severity-classified item and routes it to the right next step.
phase-scope
Defines a realistic scope for a roadmap phase using a full MoSCoW breakdown against a fixed time budget.
prd
Generates or refines a one-page Micro PRD for a product or feature in the RENATA standard.
retro
Facilitates a structured, actionable retrospective at the end of a roadmap phase or cycle, ending in an explicit decision.
todo
Manages the project's TODO backlog with inline markers in docs reconciled against a central, impact-ordered list, optionally mirrored to a task MCP.