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/plugins/mahdisanagostar/chef/claude)<a href="https://agentmods.dev/plugins/mahdisanagostar/chef/claude"><img src="https://agentmods.dev/badge/plugins/mahdisanagostar/chef/claude/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/mahdisanagostar/chef/claude"><img src="https://agentmods.dev/badge/plugins/mahdisanagostar/chef/claude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
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 1mo 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
{
"name": "chef",
"version": "0.1.0",
"description": "CHEF command and graph-first policy bundle for Claude."
}
What it installs
The manifest is a name and a version. 2 commands travel with it, and installing the plugin installs all of them — 0 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 7 lines scan A 474520aca494
chef is a plugin published in the GitHub repository mahdisanagostar/chef (2 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
obsidian-wiki
Grow an Obsidian second brain with your AI agent: ingest docs, chat history and URLs into interlinked markdown, then query it with citations. Karpathy's LLM Wiki pattern as Claude Code skills.
onebrain
OneBrain — Your AI Thinking Partner.
vault-template
Personal Knowledge Management system for Obsidian with AI-powered workflows, goal tracking, and productivity coaching.
authoring
Author text deliverables and deliver them: README / CLAUDE.md / release notes / work logs, and posting the result to Slack. Visual deliverables — slide decks, HTML documents and PDF export — live in the visuals plugin. Install at user scope to make it available across all projects.
phd-deepread-workflow
Transform academic PDFs into structured literature notes and critical-thinking canvases for Obsidian.
kb
Build and maintain LLM-powered knowledge bases as Obsidian wikis with compile, query, lint, and evolve workflows.