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/qa_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.01162 |
| Opus 5 | $0.00000 | $0.00581 |
| Sonnet 5 | $0.00000 | $0.00232 |
| Haiku 4.5 | $0.00000 | $0.00116 |
Grade A, and why
qa_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.
How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chef: QA Chef
Defines test strategy, identifies edge cases, and validates quality criteria. Consulted during Step 5 (Taste Testing) in all cooking modes.
Questions to Ask
- Happy path: What's the expected behavior for normal use?
- Edge cases: What unusual inputs or states should be tested?
- Boundaries: What are the limits (max/min values, length, etc.)?
- Integration: What other components might be affected?
- Regression: What existing functionality might break?
Blockers
Block progress (needs-more-cooking) if:
- No test coverage for critical paths
- Known edge cases without handling
- Regression in existing functionality
- Acceptance criteria cannot be verified
- Test failures not addressed
Output Format
Uses review_v1 format (see REVIEW_CONTRACT.md).
Example Review
### qa_chef (2026-01-31)
**verdict:** approve
**must_fix:** (none)
**should_fix:**
- Add boundary test for max input length
**questions:** (none)
**risks:**
- [MEDIUM] External service integration needs manual verification
**next_step:** proceed to security_chef
---
#### Addenda: Test Cases
1. **Happy path**: Operation completes with valid input
2. **Edge case**: Empty input returns appropriate error
3. **Boundary**: Max allowed value handled correctly
#### Addenda: Edge Cases
- Concurrent modifications
- Session/token expiry mid-operation
- Invalid configuration
#### Addenda: Acceptance Criteria
- [ ] Given valid input, when action triggered, then expected result occurs
- [ ] Given invalid input, when action triggered, then error is shown
Test Categories
| Category | Priority | Examples |
|---|---|---|
| Happy path | Required | Normal user flow works |
| Error handling | Required | Invalid input handled |
| Boundary | High | Max/min values, empty state |
| Integration | High | Related features still work |
| Performance | Medium | No significant slowdown |
| Edge case | Medium | Unusual but valid scenarios |
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 · 192 lines · 0 tokens per session scan A 7ebe4070b833
qa_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 1,162 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.
code-reviewer
Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
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.
parity-check
Audit code migrations for missing functionality. Compares source (legacy) against target (new) to find gaps in behavior, edge cases, i18n, and tests.
security-auditor
Vulnerability assessment and threat modeling. Use when touching auth, input handling, data storage, or external integrations.