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/security-auditgit 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.00031 | $0.00382 |
| Opus 5 | $0.00015 | $0.00191 |
| Sonnet 5 | $0.00006 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
security-audit 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 2d 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 Security Audit
You are running a comprehensive security audit. Follow these steps:
Step 1: ENVIRONMENT CHECK
Verify this is a Drupal project and identify:
- Drupal version
- Custom modules location (
web/modules/custom/) - Custom themes location (
web/themes/custom/) - Whether
composer.lockexists
Step 2: DEPENDENCY AUDIT
Run composer audit to check for known vulnerabilities in dependencies:
# DDEV
ddev composer audit
# Lando
lando composer audit
# Native
composer audit
Report any vulnerabilities found with severity levels.
Step 3: CODE AUDIT
Launch the drupal-security-auditor agent to perform deep code analysis on all custom modules and themes. The agent will check for:
- XSS vulnerabilities (Twig |raw, Markup::create with user input)
- SQL injection (string concatenation in queries)
- Access bypass (missing accessCheck, improper route permissions)
- CSRF issues (state changes via GET, missing tokens)
- File handling issues (unvalidated uploads)
- Information disclosure (debug functions, verbose errors)
- Hardcoded credentials
Step 4: REPORT
Present the combined report:
- Dependency vulnerabilities from
composer audit - Code audit findings from
drupal-security-auditor, grouped by severity - Summary with counts per severity level
- Recommended actions prioritized by risk
Format as a clear, actionable report that can be shared with the team.
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.
- 2d ago First seen · 54 lines · 31 tokens per session scan A 1474d70b7b94
security-audit is a command published in the GitHub repository abderrahimghazali/drupal-boost (1 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 382 once invoked, about $0.0002 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.