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/pjuniszewski/cook/cook-menunpx skills add PJuniszewski/cook --skill 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.00009 | $0.00693 |
| Opus 5 | $0.00005 | $0.00347 |
| Sonnet 5 | $0.00002 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00069 |
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 3d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cook-menu Skill
Interactive menu for managing cook artifacts using native Claude Code UI.
Execution Flow
When /cook-menu is invoked, follow this flow:
Step 1: Scan Artifacts
Run this command to get artifact list with metadata:
for f in cook/*.cook.md; do
if [ -f "$f" ]; then
name=$(basename "$f" .cook.md)
status=$(grep -m1 "^## Status" -A1 "$f" | tail -1 | tr -d '[:space:]')
mode=$(grep -m1 "^## Cooking Mode" -A1 "$f" | tail -1 | tr -d '[:space:]')
echo "$name|$status|$mode"
fi
done
Step 2: Select Artifact
Use AskUserQuestion tool to present artifacts:
Question: "Which artifact do you want to manage?"
Header: "Artifact"
Options: [list of artifacts with status as description]
If user selects "Exit" or cancels, end the skill.
Step 3: Select Action
Use AskUserQuestion tool to present actions:
Question: "What do you want to do with <artifact-name>?"
Header: "Action"
Options:
- "Validate" - "Run validation checks on this artifact"
- "Compare" - "Diff with another artifact"
- "Status" - "View artifact metadata summary"
- "Back" - "Return to artifact selection"
Step 4: Execute Action
Based on selection:
Validate:
./scripts/cook-validate "cook/<artifact>.cook.md" --verbose
Compare:
- Use AskUserQuestion to select second artifact
- Run:
./scripts/cook-diff "cook/<artifact1>.cook.md" "cook/<artifact2>.cook.md"
Status:
./scripts/cook-validate "cook/<artifact>.cook.md" --quiet
Then display: filename, status, mode, owner, date, section count.
Back: Return to Step 2.
Step 5: Loop
After action completes, return to Step 3 (action selection) for same artifact. User can select "Back" to return to artifact selection.
Example Flow
/cook-menu
│
▼
[AskUserQuestion: Select artifact]
- dry-run-validation.2026-01-10 (well-done)
- artifact-versioning.2026-01-10 (ready-for-merge)
│
▼ user selects "dry-run-validation"
│
[AskUserQuestion: Select action]
- Validate
- Compare
- Status
- Back
│
▼ user selects "Validate"
│
[Runs cook-validate, shows results]
│
▼
[AskUserQuestion: Select action] (loop)
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.
- 3d ago First seen · 114 lines · 9 tokens per session scan A 2e262e487a02
cook-menu is a skill published in the GitHub repository PJuniszewski/cook (13 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 693 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 skills, from other repositories
performance-optimization
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be cheaper to verify now…
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
test-driven-development
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
context-engineering
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.