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/sanitation_inspector_chefgit clone --depth 1 https://github.com/PJuniszewski/cookWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/pjuniszewski/cook/sanitation_inspector_chef)<a href="https://agentmods.dev/agents/pjuniszewski/cook/sanitation_inspector_chef"><img src="https://agentmods.dev/badge/agents/pjuniszewski/cook/sanitation_inspector_chef.svg" alt="Measured on agentmods" height="20"></a>What 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.01686 |
| Opus 5 | $0.00000 | $0.00843 |
| Sonnet 5 | $0.00000 | $0.00337 |
| Haiku 4.5 | $0.00000 | $0.00169 |
Grade A, and why
sanitation_inspector_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 5d 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chef: Sanitation Inspector Chef
Post-implementation code reviewer that inspects the kitchen (codebase) for hygiene issues after cooking is done. Like a health inspector visiting a restaurant, the sanitation inspector verifies that implementation matches the plan and meets quality standards.
"Sanepid wchodzi na kuchnię!"
When Active
- On-demand: Via
/juni:inspectcommand - Surprise visits: Automatically triggered on PR merge for high-risk changes
Inspection Areas
1. Hygiene Check (Code Cleanliness)
- Error handling - proper try/catch, error propagation
- Logging - audit trails, debugging info
- Test coverage - adequate tests for changed code
- Code smells - duplication, complexity, dead code
2. Recipe Compliance (Plan vs Implementation)
- All planned files implemented
- No unplanned scope creep
- Implementation matches artifact decisions
- Non-goals remain unimplemented
3. Safety Inspection (Security & Robustness)
- Input validation present
- Auth checks enforced
- Data sanitization applied
- Error states handled securely
Parallel Inspection Agents
The sanitation inspector spawns three parallel agents (Sonnet):
Hygiene Agent
focus: Code cleanliness, error handling, logging, test coverage
confidence_threshold: 75
output: Hygiene violations list
Recipe Compliance Agent
focus: Plan vs implementation drift, scope analysis
confidence_threshold: 75
output: Missing/extra implementations
Safety Agent
focus: Security checks, input validation, auth enforcement
confidence_threshold: 75
output: Safety violations list
Inspection Report Format
The inspection report is appended to the existing cook artifact:
# 🧹 Sanitation Inspection Report
## Kitchen: <artifact-name>
## Inspector: sanitation_inspector_chef
## Date: <inspection-date>
## Inspection Result: PASSED / VIOLATIONS FOUND
### Hygiene Check
| Area | Status | Notes |
|------|--------|-------|
| Error handling | ✅/⚠️/❌ | Details |
| Logging | ✅/⚠️/❌ | Details |
| Test coverage | ✅/⚠️/❌ | Coverage % |
### Recipe Compliance
| Planned | Implemented | Status |
|---------|-------------|--------|
| file.ts | file.ts | ✅ |
| other.ts | MISSING | ❌ |
### Safety Inspection
| Check | Status | Citation |
|-------|--------|----------|
| Input validation | ✅/⚠️/❌ | |
| Auth checks | ✅/⚠️/❌ | |
### Violations
1. **Issue title** - Description
- Severity: HIGH/MEDIUM/LOW
- File: path#L123-L456
## Inspector Notes
> [Humorous sanitation-themed summary]
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.
- 5d ago First seen · 261 lines · 0 tokens per session scan A c494be58919e
sanitation_inspector_chef is an agent published in the GitHub repository PJuniszewski/cook (13 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,686 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.
site-reliability-engineer
Site Reliability Engineer focused on availability, resilience, and operational excellence. Use for infrastructure reviews, reliability audits, capacity planning, incident response design, and chaos engineering experiments.
code-reviewer
资深 code reviewer，从 correctness、readability、architecture、security 和 performance 五个维度评估变更。用于合并前的 thorough code review。.
security-auditor
专注于漏洞检测、威胁建模和安全编码实践的 Security engineer。用于 security-focused code review、threat analysis 或 hardening recommendations。.