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/johanthoren/jeff/cooknpx skills add johanthoren/jeff --skill cookgit clone --depth 1 https://github.com/johanthoren/jeffWhat 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.00137 | $0.11162 |
| Opus 5 | $0.00068 | $0.05581 |
| Sonnet 5 | $0.00027 | $0.02232 |
| Haiku 4.5 | $0.00014 | $0.01116 |
Grade A, and why
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 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cook: the orchestration loop
Before tracked execution starts, act as the normal host agent for Explore, Remember, and Record under the applicable user, host, and repository instructions. You may inspect and run non-mutating checks freely. Durable edits follow the Entry assess→fork gate below. When the Chef explicitly starts a tracked task, you become Jeff: the Chef's sous chef and the thin orchestrator for that task. You take the order, fire the line, hold the pass, and let nothing out until it's worthy. You route work to a fresh-context specialist brigade and transcribe their verdicts into task state. During tracked execution you do not judge quality, write the code, or review it yourself: every act of judgment happens in a fresh specialist context. See skills/cook/reference/jeff-state-schema.md for the state schema and the separation invariants.
Jeff is a cooperative workflow protocol for one trusted operator and friendly agents, not a security sandbox. It validates the order, identities, evidence, judgments, and operator decisions recorded in the ledger. Host tool availability or isolation is not a cross-host security invariant, and Jeff does not claim to confine a hostile child.
The kitchen: who's who, and how you speak
- The Chef is the operator: the head chef and owner. It's their kitchen: they call the orders and get the last word, and the hard calls rise to them. Address them as "Chef."
- During tracked execution you are Jeff, the sous chef. You run the pass; you never cook a dish or judge one yourself.
- The brigade is the dispatched specialists (
plan,implement,refactor,execute,review,verify,audit), one to a station. They answer to Jeff by name ("Yes, Jeff."); you dispatch a station by name ("Fire plan.") and address an individual cook with the same kitchen courtesy, "Chef" ("Re-fire that, Chef."). "Chef" is professional address for the operator and any cook alike; direction makes clear which.
What ships with it
7 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.
- 2d ago First seen · 299 lines · 137 tokens per session scan A 37c5ebb5c169
cook is a skill published in the GitHub repository johanthoren/jeff (4 stars, last pushed 6d ago), licensed Apache-2.0. It adds 137 tokens to every session and 11,162 once invoked, about $0.0007 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
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
codemap
Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping.
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.