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 skills add mahdisanagostar/chef --skill skill-findergit 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/skills/mahdisanagostar/chef/skill-finder)<a href="https://agentmods.dev/skills/mahdisanagostar/chef/skill-finder"><img src="https://agentmods.dev/badge/skills/mahdisanagostar/chef/skill-finder/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/skills/mahdisanagostar/chef/skill-finder"><img src="https://agentmods.dev/badge/skills/mahdisanagostar/chef/skill-finder.svg" alt="Reviewed on agentmods" width="80" 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.00041 | $0.01425 |
| Opus 5.5 | $0.00016 | $0.00570 |
| Sonnet 5.5 | $0.00008 | $0.00285 |
| Haiku 4.5 | $0.00004 | $0.00143 |
Grade A, and why
skill-finder 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.
How it starts
The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Finder
Mission
Use this as Chef's automatic routing layer.
Run it:
- right after
$chef-indexfor Codex work - before choosing specialist skills in Claude work
- again whenever the task changes shape, artifact, or risk
The goal is not to list every possible skill. The goal is to engage the fewest skills that materially improve the work.
Fast Path
Do not force routing when the task is already small and obvious.
Skip specialist selection when:
- the user asks for a trivial shell action or one-command lookup
- the user names one exact skill or plugin route and no support changes execution
- the current step is a tiny follow-up inside an already-correct skill lane
Default Behavior
For every non-trivial task:
- honor explicit skill, plugin, or app requests first
- classify the task
- pick one primary skill
- add at most one execution support and one verification support
- explain the choice in one short line
- re-run the check if scope shifts
If no specialist skill clearly helps, say so and continue without forcing one.
Classification Pass
Look at seven things first:
intentbuild, review, debug, research, document, design, present, automateartifactcode, UI, deck, doc, spreadsheet, repo config, workflow, knowledge baserisksecurity, architecture, multi-module change, user-facing polish, external publishmediumterminal, browser, slides, images, docs, videofreshnesswhether direct graph read, live browsing, or current repo state mattershostCodex runtime, Codex plugin, shared Chef skill, Claude skillexplicit cuesuser-named skills, plugins, tools, output formats, or platforms
Use the matrix in references/selection-matrix.md when the answer is not obvious.
Routing Rules
1. Prefer one strong specialist
Pick narrowest skill that squarely matches task.
Good:
- frontend request ->
frontend-design - presentation request ->
talkcraft - skill creation request ->
skill-creator
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 201 lines · 41 tokens per session scan A 8d7e558edda9
skill-finder is a skill published in the GitHub repository mahdisanagostar/chef (2 stars, last pushed 6mo ago), licensed MIT. It adds 41 tokens to every session and 1,425 once invoked, about $0.0002 per session on Opus 5.5. 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 skills, from other repositories
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
patent-map
A tool for making a visual map of stored patent case notes in an Obsidian vault. Obsidian is a note-taking application that stores linked text files.
plannotator-annotate
Open Plannotator's annotation UI for a file, folder, or URL, then address the returned annotations.
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
maintenance
Investigate, adopt, and verify dependency updates — with special handling for @cyanheads/mcp-ts-core. Captures what changed, understands why, cross-references against the codebase, adopts framework improvements, syncs project skills, and runs final checks. Supports two entry modes: run the full flow end-to-end, or…
graphify
Use when the user invokes /graphify or asks to build, update, or query a knowledge graph from a folder of files (code, docs, papers, notes, images). Triggers: 'map this codebase', 'graph my notes', 'what is connected across these files', 'community detection', 'GraphRAG', incremental graph update, Neo4j/SVG/GraphML…