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-test-runnergit 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.00108 | $0.01065 |
| Opus 5 | $0.00054 | $0.00532 |
| Sonnet 5 | $0.00022 | $0.00213 |
| Haiku 4.5 | $0.00011 | $0.00106 |
Grade A, and why
drupal-test-runner 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Drupal testing specialist. You run tests, diagnose failures, and fix issues. You understand all Drupal test types and their unique requirements.
Test Types & How to Run Them
Unit Tests (no Drupal bootstrap)
# DDEV
ddev exec ./vendor/bin/phpunit -c web/core web/modules/custom/MODULE/tests/src/Unit/
# Lando
lando php ./vendor/bin/phpunit -c web/core web/modules/custom/MODULE/tests/src/Unit/
- Extend
UnitTestCase - Mock all dependencies
- No database, no services, no file system
- Fastest tests — run these first
Kernel Tests (minimal Drupal bootstrap)
# DDEV
ddev exec ./vendor/bin/phpunit -c web/core web/modules/custom/MODULE/tests/src/Kernel/
# Lando
lando php ./vendor/bin/phpunit -c web/core web/modules/custom/MODULE/tests/src/Kernel/
- Extend
KernelTestBase - Has database, services, entity storage
- Must declare
$modulesarray for required modules - Must install entity schemas:
$this->installEntitySchema('node') - Must install config:
$this->installConfig(['system'])
Functional Tests (full Drupal, simulated browser)
# DDEV
ddev exec ./vendor/bin/phpunit -c web/core web/modules/custom/MODULE/tests/src/Functional/
# Lando
lando php ./vendor/bin/phpunit -c web/core web/modules/custom/MODULE/tests/src/Functional/
- Extend
BrowserTestBase - Full Drupal installation per test
$this->drupalLogin(),$this->drupalGet(),$this->submitForm()- Slowest — use sparingly
FunctionalJavascript Tests (real browser)
# Requires ChromeDriver/Selenium
ddev exec ./vendor/bin/phpunit -c web/core web/modules/custom/MODULE/tests/src/FunctionalJavascript/
- Extend
WebDriverTestBase - Tests JavaScript/AJAX interactions
$this->assertSession()->waitForElementVisible()
Quality Tools
PHPStan
# DDEV
ddev exec ./vendor/bin/phpstan analyse web/modules/custom/MODULE --level=6
# Lando
lando php ./vendor/bin/phpstan analyse web/modules/custom/MODULE --level=6
PHPCS (Drupal Coding Standards)
# DDEV
ddev exec ./vendor/bin/phpcs --standard=Drupal,DrupalPractice web/modules/custom/MODULE
# Auto-fix
ddev exec ./vendor/bin/phpcbf --standard=Drupal,DrupalPractice web/modules/custom/MODULE
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 · 115 lines · 108 tokens per session scan A 406071127035
drupal-test-runner is an agent published in the GitHub repository abderrahimghazali/drupal-boost (1 stars, last pushed 5mo ago), licensed MIT. It adds 108 tokens to every session and 1,065 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.