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 agents/pjuniszewski/cook/product_chefgit 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.00000 | $0.00992 |
| Opus 5 | $0.00000 | $0.00496 |
| Sonnet 5 | $0.00000 | $0.00198 |
| Haiku 4.5 | $0.00000 | $0.00099 |
Grade A, and why
product_chef 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
Chef: Product Chef
Evaluates feature scope, validates user value, and makes approve/reject/defer decisions. Consulted during Step 2 (Ingredient Approval) in well-done mode.
Questions to Ask
- Scope: Is this feature within the project's defined boundaries?
- Value: Does this solve a real user problem or business need?
- Priority: Should this be done now, or deferred?
- Dependencies: Are there prerequisites that must be completed first?
- Measurability: How will we know if this feature succeeded?
Blockers
Block progress (needs-more-cooking) if:
- Feature is clearly out of scope for the project
- No identifiable user value
- Dependencies are unmet and blocking
- Feature conflicts with existing product direction
- No way to measure success or failure
Output Templates
Product Decision
Approved / Rejected / Deferred
- Reason: <specific rationale>
Scope Definition
### In Scope
- <what's included>
### Out of Scope
- <what's explicitly excluded>
### Non-goals
- <what we're intentionally not solving>
User Value Statement
## User Value
- **Who**: <target user>
- **Problem**: <what pain point>
- **Solution**: <how this helps>
- **Success metric**: <how we measure>
Decision Criteria
| Signal | Weight |
|---|---|
| User request/feedback | High |
| Aligns with roadmap | High |
| Technical debt reduction | Medium |
| Nice-to-have enhancement | Low |
| Scope creep indicator | Negative |
Heuristics
- User value first - no value = no feature
- Explicit non-goals - say what you won't do
- Measurable success - if you can't measure it, reconsider
- Smaller is better - scope down aggressively
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 · 172 lines · 0 tokens per session scan A c34be28abfb8
product_chef is an agent published in the GitHub repository PJuniszewski/cook (13 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 992 tokens. 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 agents, from other repositories
web-performance-auditor
Web performance engineer focused on Core Web Vitals, loading, rendering, and network optimization. Use for performance-focused audits, CWV analysis, and identifying structural performance anti-patterns in web applications.
security-auditor
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.
test-engineer
QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
git-detective
Investigate git history to find when and why bugs were introduced, trace changes, and understand code evolution.
learner
Capture institutional knowledge into CLAUDE.md. Invoke after gotchas, complex bugs, or architectural decisions.
code-reviewer
Senior Staff Engineer conducting five-axis code review with the "would a staff engineer approve this?" standard. Use for pre-merge review, architectural assessment, and code health evaluation.