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 commands/mahdisanagostar/chef/chef-graph-refreshgit 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-graph-refresh)<a href="https://agentmods.dev/commands/mahdisanagostar/chef/chef-graph-refresh"><img src="https://agentmods.dev/badge/commands/mahdisanagostar/chef/chef-graph-refresh.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.00080 |
| Opus 5 | $0.00000 | $0.00040 |
| Sonnet 5 | $0.00000 | $0.00016 |
| Haiku 4.5 | $0.00000 | $0.00008 |
Grade A, and why
chef-graph-refresh 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.
What it actually says
/chef-graph-refresh
Refresh Chef graph state for current project.
- Confirm
knowledge-vault/Graphify/index.mdexists. - Confirm
knowledge-vault/Graphify/graphify-out/exists. - Prefer graph index before raw source reads.
- Suggest
chef graph-refresh --project <path> --executeand note host auto-detect.
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 · 9 lines · 0 tokens per session scan A c40bf58631f8
chef-graph-refresh 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 80 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
plan-review
The core plan review flow across Claude Code, Codex, and other supported agent hosts.
obsidian-retrieval-eval
Measure how well vault search finds the right note for a natural-language question - recall@k and MRR, with the concrete failures.
obsidian-distill
Condense a long note or source into key claims, each tagged with provenance back to the exact source block it came from.
obsidian-recap
Summarize a time period from the vault - today, week, or month.
kb-ingest
Ingest external material into Sources/ inside the bound project KB, then update registry, index, and daily note as needed.
wiki-query
Ask questions against the wiki. Synthesizes answers from wiki pages with cross-reference citations.