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/quality-checkgit 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/commands/abderrahimghazali/drupal-boost/quality-check)<a href="https://agentmods.dev/commands/abderrahimghazali/drupal-boost/quality-check"><img src="https://agentmods.dev/badge/commands/abderrahimghazali/drupal-boost/quality-check.svg" alt="Measured on agentmods" 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 | $0.00023 | $0.00424 |
| Opus 5 | $0.00012 | $0.00212 |
| Sonnet 5 | $0.00005 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
quality-check 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 3d 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.
What it actually says
Drupal Code Quality Check
You are running the full quality suite on Drupal custom code. Follow these steps:
Step 1: DETERMINE SCOPE
- If
$ARGUMENTScontains a path, check that path only - If
$ARGUMENTScontains--all, check all custom code - If no arguments, check
web/modules/custom/andweb/themes/custom/
Detect the environment (DDEV/Lando) and prefix commands accordingly.
Step 2: RUN QUALITY TOOLS
Launch the drupal-test-runner agent to run all quality checks:
PHPCS (Coding Standards)
ddev exec ./vendor/bin/phpcs --standard=Drupal,DrupalPractice PATH
PHPStan (Static Analysis)
ddev exec ./vendor/bin/phpstan analyse PATH --level=6
Drupal Check (Deprecations) — if available
ddev exec ./vendor/bin/drupal-check PATH
Step 3: REPORT
Present results grouped by tool:
=== CODE QUALITY REPORT ===
## PHPCS (Coding Standards)
- Errors: X
- Warnings: Y
- [List top issues]
## PHPStan (Static Analysis)
- Errors: X
- [List top issues]
## Drupal Check (Deprecations)
- Deprecated APIs found: X
- [List deprecations]
## Summary
Total issues: X errors, Y warnings
Auto-fixable with phpcbf: Z issues
If issues are auto-fixable, offer to run phpcbf:
ddev exec ./vendor/bin/phpcbf --standard=Drupal,DrupalPractice PATH
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.
- 3d ago First seen · 69 lines · 23 tokens per session scan A ae379c3d45c6
quality-check is a command published in the GitHub repository abderrahimghazali/drupal-boost (1 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 424 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.
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.
security-audit
Audit a Drupal site for security issues and vulnerabilities.
config-export
Export Drupal configuration with proper workflow.
drush-check
Run common Drush checks to verify Drupal site health.