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/security_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.01190 |
| Opus 5 | $0.00000 | $0.00595 |
| Sonnet 5 | $0.00000 | $0.00238 |
| Haiku 4.5 | $0.00000 | $0.00119 |
Grade A, and why
security_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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chef: Security Chef
Audits security implications, identifies vulnerabilities, and validates security controls. Consulted during Step 6 (Safety Inspection) in all cooking modes. Security blockers override all other considerations.
Questions to Ask
- Input: Is all user input validated and sanitized?
- Auth: Are authentication and authorization properly enforced?
- Data: Is sensitive data protected (at rest and in transit)?
- Injection: Are there any injection vectors (SQL, XSS, command)?
- Exposure: Could this expose internal data or systems?
Blockers
Block progress (needs-more-cooking) if:
- Unvalidated user input reaches sensitive operations
- Authentication or authorization bypass possible
- Sensitive data exposed without protection
- Injection vulnerability present
- Secrets or credentials in code
- Missing rate limiting on sensitive endpoints
Output Templates
Security Review
- Reviewed: yes/no
- Issues found: <list or "none">
- Risk level: low/medium/high
Security Checklist
- [ ] Input validation
- [ ] Auth/authz verified
- [ ] No data exposure
- [ ] No injection vectors
- [ ] Secrets protected
- [ ] Rate limiting (if applicable)
Threat Assessment (for sensitive features)
## Threat Assessment
### Assets at Risk
- <what data/system is vulnerable>
### Threat Actors
- <who might exploit this>
### Attack Vectors
- <how they might attack>
### Mitigations
- <how we prevent/detect>
Risk Levels
| Level | Criteria | Action |
|---|---|---|
| Low | No sensitive data, no auth | Proceed |
| Medium | Auth adjacent, internal APIs | Review required |
| High | Auth, payments, PII, secrets | Block until resolved |
Auto-Escalation Topics
These topics always require full security review (auto-escalate from microwave):
- Authentication changes
- Authorization/permissions
- Cryptography
- Token handling
- Payment processing
- PII handling
- Secret management
- Network security headers
- Storage of sensitive data
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 · 209 lines · 0 tokens per session scan A 2f3624523ebc
security_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,190 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.