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/abderrahimghazali/drupal-boost/boost-themegit clone --depth 1 https://github.com/abderrahimghazali/drupal-boostWhat 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.00018 | $0.00510 |
| Opus 5 | $0.00009 | $0.00255 |
| Sonnet 5 | $0.00004 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
boost-theme 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 yesterday.
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
Drupal 11 Theme Scaffolding
You are creating a new Drupal 11 theme. Follow these phases:
Phase 1: DISCOVERY
Parse arguments:
$ARGUMENTS[0]= theme machine name (snake_case)
Ask the user:
- Base theme? (Starterkit, Olivero, Claro, none)
- What components are needed? (header, footer, card, hero, navigation, etc.)
- CSS methodology? (BEM, utility-first, custom)
- JavaScript needs? (vanilla, Alpine.js, etc.)
- Responsive breakpoints?
- Does the theme need custom block templates?
Phase 2: EXPLORATION
Launch a drupal-explorer agent to:
- Check existing themes in the project
- Identify existing SDCs that could be reused
- Find template suggestions and preprocess functions
- Read CLAUDE.md for project conventions
Phase 3: SCAFFOLD
Generate base theme (if using Starterkit):
php web/core/scripts/drupal generate-theme THEME_NAME --starterkit starterkit_theme
Or create manually:
THEME_NAME.info.ymlTHEME_NAME.theme(preprocess functions)THEME_NAME.libraries.yml(global CSS/JS)THEME_NAME.breakpoints.yml(responsive breakpoints)
Create SDCs:
For each requested component, create:
components/COMPONENT_NAME/
├── COMPONENT_NAME.component.yml # Props, slots, metadata
├── COMPONENT_NAME.twig # Template
├── COMPONENT_NAME.css # Styles
└── COMPONENT_NAME.js # Scripts (optional)
Create template overrides as needed:
templates/layout/page.html.twigtemplates/node/node--TYPE.html.twigtemplates/block/block--PLUGIN_ID.html.twig
Phase 4: SUMMARY
List all created files and provide next steps:
- Set as default: Admin > Appearance > Set as default
- Clear cache:
drush cr - Enable Twig debug for development
- Review SDCs in the component library
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.
- yesterday First seen · 69 lines · 18 tokens per session scan A d7261989fadd
boost-theme is a command published in the GitHub repository abderrahimghazali/drupal-boost (1 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 510 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.
Other commands, from other repositories
module-scaffold
Generate a new Drupal module with best-practice structure.
performance-check
Analyze Drupal site performance and caching configuration.
code-review
Full code review of a branch, PR, or Jira ticket. Accepts a Jira ticket ID (e.g. TICKET-123), branch name, or PR number as optional input. Defaults to current branch. Runs static analysis, PHPCS, PHPStan, and Drupal best-practice checks.
security-audit
Audit a Drupal site for security issues and vulnerabilities.
config-export
Export Drupal configuration with proper workflow.
drush-check
Run common Drush checks to verify Drupal site health.