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 natea/ExoMind --skill recipe-findinggit clone --depth 1 https://github.com/natea/ExoMindWrote 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/natea/exomind/recipe-finding)<a href="https://agentmods.dev/skills/natea/exomind/recipe-finding"><img src="https://agentmods.dev/badge/skills/natea/exomind/recipe-finding/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/natea/exomind/recipe-finding"><img src="https://agentmods.dev/badge/skills/natea/exomind/recipe-finding.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.02932 |
| Opus 5 | $0.00018 | $0.01466 |
| Sonnet 5 | $0.00007 | $0.00586 |
| Haiku 4.5 | $0.00004 | $0.00293 |
Grade A, and why
recipe-finding 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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recipe Finding & Scaling
Overview
Find recipes via web search and resize them based on number of servings. Core principle: Systematic scaling with proper fractional handling ensures accurate, usable recipes.
Announce at start: "I'm using the recipe-finding skill to search for recipes and resize portions."
Quick Reference
| Task | Steps | Key Tools |
|---|---|---|
| Find Recipe | Search → Extract → Verify yield | WebSearch, WebFetch |
| Scale Recipe | Calculate factor → Scale ingredients → Round appropriately | Math |
| Present | Original → Scaled → Instructions | Formatted output |
When to Use
Use when:
- User requests a recipe by name or type
- User wants to resize portions (e.g., "recipe for 4 people")
- User needs ingredient scaling help
- User wants dietary modifications with scaling
Don't use when:
- User wants cooking techniques only
- User wants general nutrition advice
- Creating original recipes (not finding existing ones)
The Pattern
Recipe Finding Progress:
- [ ] Phase 1: Search & Extract (recipe found with yield)
- [ ] Phase 2: Calculate Scaling (factor determined)
- [ ] Phase 3: Scale Ingredients (all items properly converted)
- [ ] Phase 4: Format Output (clear, usable recipe)
Phase 1: Search & Extract Recipe
Find recipe with clear yield information:
- Use WebSearch to find recipes
- Prioritize sources: AllRecipes, FoodNetwork, NYT Cooking, Serious Eats
- Extract complete recipe including:
- Original yield (servings or pieces)
- All ingredients with measurements
- Instructions
- Prep/cook times
Example search patterns:
"chocolate chip cookies recipe 24 cookies"
"chicken tikka masala recipe 4 servings"
"pizza dough recipe site:seriouseats.com"
Verify you have:
- ✅ Clear original yield (e.g., "Makes 24 cookies", "Serves 4")
- ✅ Complete ingredient list with measurements
- ✅ Instructions
Phase 2: Calculate Scaling Factor
Formula: Scaling Factor = Desired Servings ÷ Original Servings
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 First seen · 323 lines · 36 tokens per session scan A 237686a3e1b1
recipe-finding is a skill published in the GitHub repository natea/ExoMind (21 stars, last pushed 10mo ago), licensed MIT. It adds 36 tokens to every session and 2,932 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…