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.
git clone --depth 1 https://github.com/abderrahimghazali/drupal-boostWrote 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/agents/abderrahimghazali/drupal-boost/drupal-explorer)<a href="https://agentmods.dev/agents/abderrahimghazali/drupal-boost/drupal-explorer"><img src="https://agentmods.dev/badge/agents/abderrahimghazali/drupal-boost/drupal-explorer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/abderrahimghazali/drupal-boost/drupal-explorer"><img src="https://agentmods.dev/badge/agents/abderrahimghazali/drupal-boost/drupal-explorer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00103 | $0.00720 |
| Opus 5.5 | $0.00041 | $0.00288 |
| Sonnet 5.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 1mo 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.
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.
- 1mo ago 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 6mo ago), licensed MIT. It adds 103 tokens to every session and 720 once invoked, about $0.0004 per session on Opus 5.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
call-tracer
Orchestrates parallel call tree tracing using subagents for each entry point category (Controllers, LiveViews, Workers, GenServers). Use proactively when debugging unexpected values, tracing request flow, or planning signature changes.
do-debugger
Autonomous Durable Objects debugger. Automatically detects and fixes DO configuration errors, runtime issues, and common mistakes without user intervention.
better-auth-debugger
Autonomous agent for diagnosing better-auth authentication issues. Analyzes configuration, validates OAuth callbacks, tests endpoints, and provides specific fixes.
bug-detector
Detects correctness bugs, logic errors, edge cases, API misuse, and error handling issues in code changes.
queue-doctor
Use this agent when background-job or message-consumer code needs an at-least-once reliability audit, a worker with no dead-letter queue, no idempotency/dedup store, no retry backoff, an ack before the work is done, or an event published without a transactional outbox. Trigger phrases include "audit my queue", "are my…
drupal-performance-engineer
Use this agent when you need to diagnose and resolve Drupal performance issues including slow page renders, cache invalidation problems, database query bottlenecks, or infrastructure tuning. Examples include: profiling a slow node view and optimizing cache contexts, analyzing Redis miss ratios and adjusting bin…