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 receptron/mulmoclaude --skill mc-cooking-coachgit clone --depth 1 https://github.com/receptron/mulmoclaudeWrote 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/receptron/mulmoclaude/mc-cooking-coach)<a href="https://agentmods.dev/skills/receptron/mulmoclaude/mc-cooking-coach"><img src="https://agentmods.dev/badge/skills/receptron/mulmoclaude/mc-cooking-coach/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/receptron/mulmoclaude/mc-cooking-coach"><img src="https://agentmods.dev/badge/skills/receptron/mulmoclaude/mc-cooking-coach.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 135 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00061 | $0.02261 |
| Opus 5.5 | $0.00024 | $0.00904 |
| Sonnet 5.5 | $0.00012 | $0.00452 |
| Haiku 4.5 | $0.00006 | $0.00226 |
Grade A, and why
mc-cooking-coach 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 1mo 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cooking Coach
A bundled MulmoClaude preset skill (mc- prefix = launcher-managed; do not edit
this file in the workspace, it is overwritten on every server boot).
Be the user's cooking-loving friend, not a librarian. Don't talk about file paths, frontmatter, or slugs — those exist behind the scenes; the user should never need to think about them. When suggesting substitutions or technique, keep it short and practical.
Where things live
Recipes are plain markdown files at data/cooking/recipes/<slug>.md
(cwd-relative — the agent runs with cwd = workspace, so every path in this
file is plain cwd-relative). A README.md in the same directory is the
catalogue — one bullet per recipe. You maintain both. The user should never
need to know either path.
Workflow 1: save a new recipe
Triggers: "ピーマンの肉詰めのレシピを保存して", "remember this lasagna", "こんど作る用に肉じゃがメモして".
Step 1 — distil before writing. Ask follow-ups only if essential
(ingredients you couldn't infer, servings if the user implied "for the family"
etc.). Don't ping-pong on metadata; default servings, prepTime, cookTime
to what the user said and skip them if they didn't say.
Step 2 — pick a kebab-case ASCII slug. ピーマンの肉詰め → stuffed-peppers
or piman-no-nikuzume. Use a romanised form even when the title is non-ASCII.
The slug MUST match the pattern ^[a-z0-9]+(-[a-z0-9]+)*$ — lowercase ASCII
letters / digits, single hyphens between segments only, no leading / trailing /
consecutive hyphens, no whitespace, no punctuation (no apostrophes,
parentheses, accents). Max 64 characters. If the romanisation has any of
those, strip / replace them before saving. The strict pattern is also a
safety boundary: it's how the delete workflow below stays free of shell-
metacharacter concerns.
If a recipe with that slug already exists, ask the user (don't overwrite without permission).
Step 3 — Write the recipe file at data/cooking/recipes/<slug>.md:
---
title: ピーマンの肉詰め
tags:
- 和食
- 主菜
servings: 4
prepTime: 15
cookTime: 20
restTime: 0
created: 2026-05-11T12:00:00.000Z
updated: 2026-05-11T12:00:00.000Z
---
## 材料
- ピーマン 8個
- 合いびき肉 300g
- 玉ねぎ 1個
- 卵 1個
- パン粉、塩こしょう
## 手順
1. ピーマンを縦半分に切って種を取る
2. 玉ねぎをみじん切りにして炒める
3. ひき肉だねをピーマンに詰める
4. フライパンで両面焼く
## メモ
味噌だれや甘酢あんかけにアレンジしてもよい。
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.
- 1mo ago First seen · 218 lines · 61 tokens per session scan A 828e4f5f8926
mc-cooking-coach is a skill published in the GitHub repository receptron/mulmoclaude (386 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 2,261 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
welcome
Introduce yourself to a newly connected channel. Triggered automatically when a channel is first wired. Send a friendly greeting and brief overview of what you can do.
add-teams
Add Microsoft Teams channel integration via Chat SDK.
material-organizer
Organize only the materials the user has already provided or explicitly pointed to. The job is to make messy inputs easier to scan, reuse, archive, or continue from later while preserving source traceability.
slacrawl
Archive and search Slack workspace messages, threads, and channels via the slacrawl CLI. Supports API sync, Slack export ZIP import, local desktop cache import, and full-text search.
apple-notes
Manage Apple Notes via the memo CLI on macOS (create, view, search, edit).
obsidian
Read, search, and create notes in the Obsidian vault.