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-modulegit 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.00024 | $0.00638 |
| Opus 5 | $0.00012 | $0.00319 |
| Sonnet 5 | $0.00005 | $0.00128 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
boost-module 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drupal 11 Module Scaffolding
You are scaffolding a new Drupal 11 module. Follow these phases:
Phase 1: DISCOVERY
Parse the arguments:
$ARGUMENTS[0]= module machine name (snake_case)$ARGUMENTS[1]= module description (optional)
Ask the user what the module needs:
- What does the module do?
- Does it need custom entities? (content entity, config entity)
- Does it need routes/pages? (controllers, forms)
- Does it need plugins? (blocks, fields, queue workers)
- Does it need services?
- Does it need hooks?
- Does it need REST/API endpoints?
- Does it need configuration? (admin settings form)
Phase 2: EXPLORATION
Launch a drupal-explorer agent to:
- Check for existing modules with similar functionality
- Identify patterns and conventions used in the project
- Find services and entities that the new module should interact with
- Read CLAUDE.md for project-specific conventions
Phase 3: ARCHITECTURE
Launch a drupal-architect agent to:
- Design the module architecture based on requirements
- Propose file structure, services, entities, plugins
- Identify which Drupal APIs to use
- Plan the dependency injection graph
Present the architecture to the user for approval.
Phase 4: IMPLEMENTATION
Scaffold all files based on the approved architecture:
Always create:
MODULE_NAME.info.yml
Create as needed:
MODULE_NAME.services.yml(if services are needed)MODULE_NAME.routing.yml(if routes are needed)MODULE_NAME.permissions.yml(if custom permissions)MODULE_NAME.links.menu.yml(if menu items)MODULE_NAME.libraries.yml(if CSS/JS)src/classes (controllers, forms, services, entities, plugins)config/schema/(config schema for any configuration)config/install/(default configuration)templates/(Twig templates)tests/src/Unit/(unit tests)tests/src/Kernel/(kernel tests)
Phase 5: QUALITY REVIEW
Launch drupal-reviewer to check the scaffolded code for:
- Coding standards compliance
- Proper DI patterns
- Complete cache metadata
- Config schema correctness
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 · 84 lines · 24 tokens per session scan A 1bd1449f1e7f
boost-module is a command published in the GitHub repository abderrahimghazali/drupal-boost (1 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 638 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.
security-audit
Audit a Drupal site for security issues and vulnerabilities.
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.
config-export
Export Drupal configuration with proper workflow.
drush-check
Run common Drush checks to verify Drupal site health.