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 skills/florianbruniaux/claude-code-plugins/recipe-templatenpx skills add FlorianBruniaux/claude-code-plugins --skill recipe-templategit clone --depth 1 https://github.com/FlorianBruniaux/claude-code-pluginsWrote 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/florianbruniaux/claude-code-plugins/recipe-template)<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-plugins/recipe-template"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/recipe-template.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.00051 | $0.00562 |
| Opus 5 | $0.00026 | $0.00281 |
| Sonnet 5 | $0.00010 | $0.00112 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
recipe-template 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
Recipe Command Template
This is a template. Replace all
[placeholder]content with your specifics.
When to Use
- [Describe the exact situation where this command applies]
- [Describe when NOT to use it, with a common misuse case]
Context Validation Checkpoints
Before executing any step, verify all of these are true. If any checkpoint fails, stop and explain why to the user.
- [Precondition 1: e.g., "The target branch exists and is up to date with main"]
- [Precondition 2: e.g., "No uncommitted changes in the affected files"]
- [Precondition 3: e.g., "Required config file exists at path X"]
- [Precondition 4: e.g., "Necessary permissions or credentials are available"]
Recipe Steps
Step 1: [Action name]
[Clear instructions for this step. Be specific about what to read, what to check, what to write.]
Validation: [How Claude verifies this step completed correctly before moving to Step 2]
Step 2: [Action name]
[Instructions]
Validation: [How to verify]
Step 3: [Action name]
[Instructions]
Validation: [How to verify]
Step 4: Confirm Completion
Summarize what was done:
- [Item 1 completed]
- [Item 2 completed]
- Files modified: [list]
- Next action for the user (if any): [instruction]
Error Handling
| Situation | Response |
|---|---|
| [Error condition 1] | [What to do: retry / stop / ask user] |
| [Error condition 2] | [What to do] |
| Precondition checkpoint fails | Stop. Explain which checkpoint failed and what the user needs to fix before re-running |
Arguments
If $ARGUMENTS[0] was provided: [how to use it]
If no argument was provided: [default behavior]
The "Context Validation Checkpoints" section is the key pattern from this template. It forces Claude to verify preconditions explicitly rather than discovering failures mid-execution. Inspired by recurring patterns in Packmind commands (Apache 2.0).
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 · 79 lines · 51 tokens per session scan A 087e1cec3f48
recipe-template is a skill published in the GitHub repository FlorianBruniaux/claude-code-plugins (40 stars, last pushed 3d ago), licensed MIT. It adds 51 tokens to every session and 562 once invoked, about $0.0003 per session on Opus 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-30.
Other skills, from other repositories
vc-autopilot
Emit and validate the provisional goal block for Autopilot Mode. Owns the 9-field format and resume detection from a pasted goal block.
vc-problem-solving
Apply systematic problem-solving techniques when stuck. Use for complexity spirals, innovation blocks, recurring patterns, assumption constraints, simplification cascades, scale uncertainty.
thoroughness-scoring
Score every decision point with a Thoroughness Rating (1-10). AI makes the marginal cost of doing things properly near-zero — pick the higher-rated option every time. Includes scope checks to distinguish contained vs unbounded work.
report
Read the delivery log and say which rules actually fire, which never have, and what to prune or fix. Use when the user asks whether ballast is doing anything, wants to clean up their rule catalog, or on a periodic review.
orchestrate
Wire Commands, Agents, and Skills together for complex features. Use when building features that need research, planning, and implementation phases.
squid-self-improve
Analyze developer corrections from the current coding session and persist lessons learned as rules in AGENTS.md files or memory. Use at the end of a session after the developer corrected your work, when they say "squid-self-improve", ask to capture what was learned, or ask you to reflect on mistakes and extract…