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 commands/pjuniszewski/cook/cook-menugit clone --depth 1 https://github.com/PJuniszewski/cookWhat 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.00006 | $0.00380 |
| Opus 5 | $0.00003 | $0.00190 |
| Sonnet 5 | $0.00001 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
cook-menu 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.
What it actually says
/cook-menu Command
Interactive artifact management menu for cook artifacts.
Usage
/cook-menu
What It Does
Launches an interactive terminal menu for managing cook artifacts:
- Lists all artifacts in
cook/*.cook.md - Shows status for each (well-done, cooking, blocked, etc.)
- Provides actions:
- Validate artifact
- Compare/diff artifacts
- View status summary
Execution
When /cook-menu is invoked, run:
./scripts/cook-menu
Menu Flow
┌─────────────────────────────────────┐
│ Select artifact: │
│ [1] feature-x.2026-01-10 │
│ [2] bugfix-y.2026-01-09 │
│ [0] Exit │
└─────────────────────────────────────┘
│
▼
┌─────────────────────────────────────┐
│ Select action: │
│ [1] ✓ Validate │
│ [2] ⇄ Compare │
│ [3] ℹ Status │
│ [0] Back │
└─────────────────────────────────────┘
Actions
| Action | Description |
|---|---|
| Validate | Runs cook-validate on selected artifact |
| Compare | Runs cook-diff between two artifacts |
| Status | Shows artifact metadata summary |
Requirements
scripts/cook-menumust exist and be executablescripts/cook-validatefor validationscripts/cook-difffor comparisons- Artifacts in
cook/*.cook.md
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 · 68 lines · 6 tokens per session scan A d96bbf6f04f3
cook-menu is a command published in the GitHub repository PJuniszewski/cook (13 stars, last pushed 6mo ago), licensed MIT. It adds 6 tokens to every session and 380 once invoked, about $0.0000 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-30.
Other commands, from other repositories
ship
Run the pre-launch checklist via parallel fan-out to specialist personas, then synthesize a go/no-go decision.
build
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
constraints
Define and enforce this project's quality bar — interview, sane defaults, CONSTRAINTS.md.
webperf
Run a web performance audit via the web-performance-auditor persona.
plan
Break work into small verifiable tasks with acceptance criteria and dependency ordering.
review
Conduct a five-axis code review — correctness, readability, architecture, security, performance.