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 skills/proxy2021/enso/recipe_managernpx skills add Proxy2021/Enso --skill recipe_managergit clone --depth 1 https://github.com/Proxy2021/EnsoWhat 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 | $0.00015 | $0.00634 |
| Opus 5 | $0.00008 | $0.00317 |
| Sonnet 5 | $0.00003 | $0.00127 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
recipe_manager 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recipe Manager
Recipe discovery, organization, meal planning with nutritional info and collections
Available Tools
enso_recipe_manager_search_recipes (primary)
Search for recipes by keyword, ingredient, cuisine type, dietary restriction, or meal type. Returns paginated results with images, titles, prep time, and ratings.
Parameters:
query(string): Search query: keyword, ingredient, dish name, cuisine, or dietary preferencecuisine(string): Filter by cuisine type (e.g. italian, mexican, japanese, indian)dietary(string): Filter by dietary restriction (e.g. vegetarian, vegan, gluten-free, keto, paleo)mealType(string): Filter by meal type (e.g. breakfast, lunch, dinner, snack, dessert)maxTime(number): Maximum total time in minuteslimit(number): Max number of results (default 10)
enso_recipe_manager_view_recipe
Display full recipe details: ingredients with quantities, step-by-step instructions, prep/cook time, servings, cuisine tags, and dietary labels.
Parameters:
query(string): Recipe name or search query to find and display the recipeservings(number): Number of servings to scale the recipe to
enso_recipe_manager_get_nutrition
Look up detailed nutritional information for a recipe or ingredient: calories, protein, carbs, fat, fiber, sugar, sodium, and vitamins/minerals. Supports per-serving and per-recipe views.
Parameters:
query(string): Recipe name or ingredient to look up nutrition forservings(number): Number of servings (for per-serving calculation)viewMode(string): View mode: 'serving' for per-serving or 'recipe' for total recipe
enso_recipe_manager_save_recipe
Save a recipe to a personal collection with custom tags, notes, and rating. Organize into collections like 'Weeknight Dinners', 'Holiday Favorites'.
Parameters:
recipeName(string): Name of the recipe to saverecipeData(string): JSON string of the full recipe datacollection(string): Collection name to save to (e.g. 'Weeknight Dinners', 'Quick Meals')tags(string): Comma-separated tags (e.g. 'easy,chicken,pasta')notes(string): Personal notes about the reciperating(number): Personal rating 1-5
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 · 61 lines · 15 tokens per session scan A e0129affc72c
recipe_manager is a skill published in the GitHub repository Proxy2021/Enso (5 stars, last pushed 3mo ago), licensed MIT. It adds 15 tokens to every session and 634 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-08-31.
Other skills, from other repositories
clawteam
Multi-agent swarm orchestration. USE THIS (not delegatetask) when the user says team/swarm/multi-agent/clawteam/parallel-agents/agent-team, or asks for multi-perspective analysis (stocks, research, code review, strategy). Spawns N Hermes workers in tmux windows with git worktree isolation, file-based inboxes, and a…
clawteam
Multi-agent swarm coordination via the ClawTeam CLI. Use when the user wants to create agent teams, spawn multiple agents to work in parallel, coordinate tasks with dependencies, broadcast messages between agents, monitor progress via kanban board, or launch pre-built team templates (hedge-fund, code-review…
openclaw-plugin
This plugin is a thin adapter between OpenClaw and LycheeMem. It does not replace memory-core, does not claim plugins.slots.memory, and does not duplicate LycheeMem algorithms.
lycheemem
Forceful operating rules for using LycheeMem as the primary structured long-term memory path inside OpenClaw.
memory
Use LycheeMem as Claude Code's structured long-term memory for prior conversations, user preferences, project decisions, timelines, and durable facts.
tweetclaw
OpenClaw guide for Twitter search, follower exports, monitoring, media, and approved X automation through Xquik. Not affiliated with X Corp.