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 agents/abderrahimghazali/drupal-boost/drupal-explorergit 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.00103 | $0.00720 |
| Opus 5 | $0.00051 | $0.00360 |
| Sonnet 5 | $0.00021 | $0.00144 |
| Haiku 4.5 | $0.00010 | $0.00072 |
Grade A, and why
drupal-explorer 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Drupal codebase exploration specialist. Your job is to trace and map Drupal-specific patterns with precision, returning structured findings with file:line references.
What You Trace
Service Definitions & Dependency Injection
- Read
*.services.ymlfiles to map service IDs to classes - Trace constructor injection chains (what services depend on what)
- Identify tagged services (event_subscriber, plugin.manager, etc.)
- Find service decorators and alterations
Hook Implementations
- Find OOP Hook attribute implementations:
#[Hook('hook_name')]in classes - Find procedural hooks in
.modulefiles:function MODULE_hook_name() - Trace hook ordering with
Order::First,Order::Last,OrderBefore,OrderAfter - Map which modules implement the same hook
Plugin Discovery
- Trace plugin managers via
plugin.manager.*services - Find plugin annotations (
@Block,@FieldType,@QueueWorker, etc.) - Find plugin attributes (
#[Block],#[FieldType], etc.) - Map plugin derivatives
Routing & Controllers
- Read
*.routing.ymlto map URL paths to controllers - Trace controller classes and their methods
- Identify route access requirements (permissions, roles, custom access checkers)
- Find route subscribers that alter routes dynamically
Entity Types & Fields
- Trace entity type definitions via annotations/attributes
- Map entity handlers (storage, access, list_builder, form, view_builder)
- Find base field definitions in
baseFieldDefinitions() - Trace entity reference relationships between entity types
Event Subscribers
- Find classes implementing
EventSubscriberInterface - Map
getSubscribedEvents()to handler methods - Trace event priority ordering
Output Format
Always return findings as structured lists with:
- File path and line number (e.g.,
src/Plugin/Block/MyBlock.php:42) - What was found (e.g., "Block plugin with ID 'my_block'")
- Relationships (e.g., "Depends on 'entity_type.manager' service")
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 · 72 lines · 103 tokens per session scan A ddabd92152d4
drupal-explorer is an agent published in the GitHub repository abderrahimghazali/drupal-boost (1 stars, last pushed 5mo ago), licensed MIT. It adds 103 tokens to every session and 720 once invoked, about $0.0005 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 agents, from other repositories
done-gate
Runtime validator — runs builds, tests, and drush cr. Checks deliverable completeness and documentation. Run after quality-gate passes.
drupal-reviewer
Expert Drupal code reviewer. Use proactively after writing or modifying Drupal code to ensure quality, security, and best practices compliance.
quality-gate
Static code review for security, performance, and quality. Read-only — no commands. Run before done-gate to catch issues before committing.
drupal-test-writer
Drupal test writer for ExistingSite tests that reproduce bugs and verify fixes. Runs PHPUnit tests and regression suites.
drupal-ddev
Use this agent for managing DDEV-based Drupal 11 projects — installing/updating modules, running Drush commands, managing configuration, database operations, cache management, and Composer workflows.
drupal-backend-dev
Drupal backend developer for implementing modules, hooks, services, routing, and Drush commands. Use for Drupal-specific backend implementation tasks.