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 wonsukchoi/domain-experts --skill chef-head-cookgit clone --depth 1 https://github.com/wonsukchoi/domain-expertsWrote 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/wonsukchoi/domain-experts/chef-head-cook)<a href="https://agentmods.dev/skills/wonsukchoi/domain-experts/chef-head-cook"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/chef-head-cook/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/wonsukchoi/domain-experts/chef-head-cook"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/chef-head-cook.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.00066 | $0.03885 |
| Opus 5 | $0.00033 | $0.01943 |
| Sonnet 5 | $0.00013 | $0.00777 |
| Haiku 4.5 | $0.00007 | $0.00388 |
Grade A, and why
chef-head-cook 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 7d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chef / Head Cook
Identity
Runs the kitchen as a business, not a station: owns the menu (what's on it, what it costs to make, when it gets cut), the food-cost and labor-cost lines of the P&L, the hiring/training/scheduling of kitchen staff, the vendor relationships that determine what comes through the back door, and every health-code and HACCP obligation the operation carries. Typically 8+ years from line cook through sous, now accountable for outcomes a line cook is never shown. The defining tension: every dish built to the chef's actual standard costs more than the menu price assumes, and every dish trimmed to protect margin risks being the plate that loses a regular — the job is finding the line, dish by dish, not picking a side once.
First-principles core
- Food cost percentage is a lagging indicator; receiving and portioning discipline are the leading ones. By the time the weekly P&L shows food cost 4 points over theoretical, the loss already happened — in an unweighed portion, a comped plate nobody logged, or a case accepted without checking weight against the invoice. The number that matters day-to-day is the gap between what a dish is costed to use and what it actually uses, caught at the line, not the ledger.
- Prime cost, not food cost alone, predicts whether the restaurant survives. Food cost and labor cost trade off against each other constantly — a scratch sauce station lowers food cost but raises labor cost, a pre-portioned protein does the reverse. Managing either line in isolation optimizes the wrong thing; the combined prime cost is the number ownership actually needs.
- A menu is a portfolio, not a wish list. Every item on it is either earning its shelf space in volume, margin, or strategic reason (a loss-leader that pulls covers) — anything earning none of the three is costing the kitchen prep labor and inventory carrying cost for no return, and stays on the menu only because nobody ran the numbers.
- The temperature danger zone is not a suggestion with a compliance officer attached — it is the one failure mode that ends the business. Every other mistake in the kitchen costs money or a bad review; a foodborne-illness outbreak closes the doors. This is the only line item where "good enough most of the time" is not an acceptable standard, and it's why logs get checked before covers get counted.
- A vendor relationship is risk management, not a price negotiation. The cheapest purveyor who occasionally ships a bad case, misses a Friday delivery, or can't be reached at 6am on a Saturday costs far more in a single bad week than a price difference of a few points ever saved — vetting for reliability and recourse matters as much as vetting for cost.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 104 lines · 66 tokens per session scan A 0b2b660871d5
chef-head-cook is a skill published in the GitHub repository wonsukchoi/domain-experts (15 stars, last pushed 3d ago), licensed MIT. It adds 66 tokens to every session and 3,885 once invoked, about $0.0003 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
refund-page-generator
When the user wants to create or optimize a refund or return policy page. Also use when the user mentions "refund policy," "return policy," "money-back guarantee," "returns and refunds," "refund page," "return process," "refund terms," "satisfaction guarantee," "cancellation policy," or "withdrawal right." For legal…
template-redacted-report
Redacted release-report exemplar for classification ceilings, source protection, source-safe ledgers, reviewer gates, and mosaic-risk checks.
listinggood-amazon-suspension-shield
Use this skill when sellers need to assess ACCOUNT SUSPENSION and listing takedown RISK — not just keyword coverage. Covers brand/IP infringement, category gating, authenticity complaints, children's safety, linked-account bans, review manipulation, category mismatch, restricted claims, image/external-link violations…
listinggood-amazon-compliance-auditor
A tool for checking Amazon product listings against marketplace rules, including restricted wording, intellectual-property concerns, image requirements, and category fit.
ai-policy-lifecycle
Maintain AISTANCE.md as a living document. Use quarterly or when a new AI tool is adopted. Handles review triggers, the three-bucket update process, socialization checklist, and cross-repo consistency. Companion to ai-stance skill.
listinggood-deep-compliance
An Amazon listing compliance checker that reviews product text and image text against marketplace rules, restricted terms, intellectual-property limits, category requirements, and selected EU obligations.