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-discover)<a href="https://agentmods.dev/commands/shinpr/nautilus/recipe-discover"><img src="https://agentmods.dev/badge/commands/shinpr/nautilus/recipe-discover.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.00010 | $0.00039 |
| Opus 5 | $0.00005 | $0.00019 |
| Sonnet 5 | $0.00002 | $0.00008 |
| Haiku 4.5 | $0.00001 | $0.00004 |
Grade A, and why
recipe-discover 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.
What it actually says
Load the recipe-discover 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.
- 2d ago First seen · 8 lines · 10 tokens per session scan A 71a4246ae6fc
recipe-discover is a command published in the GitHub repository shinpr/nautilus (4 stars, last pushed 6d ago), licensed MIT. It adds 10 tokens to every session and 39 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.
assumption-test
Surfaces the riskiest business assumption behind the PRD and designs the cheapest test to falsify it before building.
hypothesis-check
Confronts each PRD hypothesis with the real measured number, forces an explicit verdict, and triggers a concrete action.
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.
discovery
Step 0 — converges a vague intuition into a clear problem (5-whys + JTBD + why-now), teaching each framework as it goes, and seeds clues for persona/journey/metrics. The pre-PRD discovery step.