boost-recipe

boost-recipe is a command for coding agents from abderrahimghazali/drupal-boost. It costs 17 tokens per session (353 once invoked), scanned A, original, MIT.

A guided scaffold for a Drupal Recipe, which is a reusable set of installation and configuration steps for a Drupal site.

In plain words
What is it for?
Use it to create a recipe that installs modules or themes, applies configuration, and can be tested with Drush on a clean site.
Why use it?
It turns the details of a site setup into a structured recipe and checks that referenced modules, recipes, and configuration actions are valid.

Command

Part of the drupal-boost plugin — 13 skills, 8 commands, 6 agents, 3 hooks shipped together

Install

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.

agentmods
npx agentmods add commands/abderrahimghazali/drupal-boost/boost-recipe
Clone the repo
git clone --depth 1 https://github.com/abderrahimghazali/drupal-boost

Or install drupal-boost, the plugin that ships this one along with the rest of its 13 skills, 8 commands, 6 agents, 3 hooks.

Wrote 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.

agentmods badge for boost-recipe

README.md
[![agentmods](https://agentmods.dev/badge/commands/abderrahimghazali/drupal-boost/boost-recipe.svg)](https://agentmods.dev/commands/abderrahimghazali/drupal-boost/boost-recipe)
Your own site
<a href="https://agentmods.dev/commands/abderrahimghazali/drupal-boost/boost-recipe"><img src="https://agentmods.dev/badge/commands/abderrahimghazali/drupal-boost/boost-recipe.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 353 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.00353
Opus 5 $0.00009 $0.00177
Sonnet 5 $0.00003 $0.00071
Haiku 4.5 $0.00002 $0.00035

Measured 4d ago against content hash 1afc0d5cbc85, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

boost-recipe 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 4d 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.

commands/boost-recipe.md · 64 lines

What it actually says

Drupal Recipe Scaffolding

You are creating a Drupal Recipe. Follow these steps:

Step 1: REQUIREMENTS

Ask the user:

  • What is the recipe's purpose? (e.g., "Set up a blog", "Configure media handling")
  • What modules should be installed?
  • What themes should be installed/set as default?
  • What configuration should be applied?
  • Should this recipe depend on other recipes?

Step 2: SCAFFOLD

Create the recipe directory:

recipes/RECIPE_NAME/
├── recipe.yml
└── config/          # Optional: config files to import

recipe.yml structure:

name: 'Recipe Name'
description: 'What this recipe sets up.'
type: 'Category'

install:
  - module_one
  - module_two

recipes:
  - core/recipes/standard  # Optional: base recipes

config:
  actions:
    # Create or update config as needed

Step 3: VALIDATE

Check that:

  • All referenced modules exist in composer.json
  • All referenced recipes exist
  • Config actions use valid syntax
  • Recipe can be applied: drush recipe recipes/RECIPE_NAME

Step 4: SUMMARY

Provide:

  1. Apply command: drush recipe recipes/RECIPE_NAME
  2. What the recipe installs and configures
  3. How to test on a clean site
Changes

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.

  1. 4d ago First seen · 64 lines · 17 tokens per session scan A 1afc0d5cbc85

Subscribe to this mod's changes

boost-recipe is a command published in the GitHub repository abderrahimghazali/drupal-boost (1 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 353 once invoked, about $0.0001 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-31.