Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/abderrahimghazali/drupal-boostnpx agentmods add agents/abderrahimghazali/drupal-boost/drupal-test-runnerWrote 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-test-runner)<a href="https://agentmods.dev/agents/abderrahimghazali/drupal-boost/drupal-test-runner"><img src="https://agentmods.dev/badge/agents/abderrahimghazali/drupal-boost/drupal-test-runner/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-test-runner"><img src="https://agentmods.dev/badge/agents/abderrahimghazali/drupal-boost/drupal-test-runner.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.00108 | $0.01065 |
| Opus 5.5 | $0.00043 | $0.00426 |
| Sonnet 5.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 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 — 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.
- 1mo ago 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 6mo ago), licensed MIT. It adds 108 tokens to every session and 1,065 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
coverage-analyst
Test coverage analysis expert. Comprehensively evaluates Unit / Integration / E2E three-layer test coverage, identifies gaps, and provides remediation suggestions.
evolve-bug-reproduction
Bug reproduction agent for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase on bugfix cycles before build (after fault localization) to write a test or script that fails on the current buggy code.
e2e-finding-verifier
Use after e2e-reviewer or scan.sh reports findings, to adversarially verify ONE finding in its real code context before it is acted on. Give it the pattern ID, file:line, and the flagged snippet; it reads the surrounding spec, project config, and the pattern contract, tries to REFUTE the finding first, and returns…
debugger
Root-cause debugging: reproduce, confirm the cause with evidence, apply a minimal fix and prove it with a regression test. Use for bugs, flaky tests or errors of unknown cause.
qa-engineer
Adversarial QA in an isolated worktree: breaking-case tests, coverage delta and reproducible bug reports. Use to test a feature, close coverage gaps or verify a fix.
distributed-test-engineer
Diagnoses and fixes distributed system test failures in NATS JetStream, pytest-asyncio fixture scoping, MCP transport lifecycles, and asyncio event loop conflicts. Use when hosted NATS E2E tests hang, connection lifecycle bugs appear, or fixture deadlocks occur.