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.
git clone --depth 1 https://github.com/mahdisanagostar/chefWrote 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/commands/mahdisanagostar/chef/chef-pack-status)<a href="https://agentmods.dev/commands/mahdisanagostar/chef/chef-pack-status"><img src="https://agentmods.dev/badge/commands/mahdisanagostar/chef/chef-pack-status.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.1 | $0.00000 | $0.00031 |
| Opus 5 | $0.00000 | $0.00015 |
| Sonnet 5 | $0.00000 | $0.00006 |
| Haiku 4.5 | $0.00000 | $0.00003 |
Grade A, and why
chef-pack-status 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 8d 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-pack-status
Show Chef pack registry and whether each pack belongs to core, security, review, UX, research, media, or business.
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.
- 8d ago First seen · 4 lines · 0 tokens per session scan A 71e4eb443e82
chef-pack-status is a command published in the GitHub repository mahdisanagostar/chef (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 31 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-31.
Other commands, from other repositories
zotero-review
Read and analyze papers from a Zotero collection, then synthesize them into the bound Obsidian project knowledge base or markdown review outputs.
kb-literature-review
Run the project-scoped literature workflow from Sources/Papers into Knowledge, Writing, and Maps/literature.canvas.
kb-ingest
Ingest external material into Sources/ inside the bound project KB, then update registry, index, and daily note as needed.
kb-links
Repair or strengthen wikilinks among canonical KB notes without generating extra artifact sprawl.
kb-log
Update the current project Daily note and, when needed, the plan, hub, and runtime binding summary.
kb-map
Generate or repair derived KB artifacts such as literature.canvas, optional Bases, or other explicit map outputs.