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/edutrul/drupal-ai/security-auditgit clone --depth 1 https://github.com/edutrul/drupal-aiWhat 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.00013 | $0.01142 |
| Opus 5 | $0.00006 | $0.00571 |
| Sonnet 5 | $0.00003 | $0.00228 |
| Haiku 4.5 | $0.00001 | $0.00114 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drupal Security Audit
Perform a comprehensive security audit of the Drupal site.
Usage: /security-audit [path]
If a path is provided, focus the audit on that module or directory. Otherwise, audit the entire site.
Path note: Commands below use
docroot/as the web root. Adjust to match your project layout (common alternatives:web/,html/).
Audit Steps
1. Check Module Security Updates
drush pm:security
Review any modules with known security vulnerabilities. These should be updated immediately.
2. Check All Outdated Modules
composer outdated drupal/*
Outdated modules may have unpatched vulnerabilities even without security advisories.
3. Review User Permissions
drush role:list
drush user:role:list --roles=administrator
Check for:
- Users with administrator role who shouldn't have it
- Overly permissive anonymous/authenticated user permissions
- Unused roles that should be removed
4. Check File Permissions
# Check settings.php is not writable
ls -la docroot/sites/default/settings.php
# Check files directory permissions
ls -la docroot/sites/default/files/
# Look for PHP files in files directory (should be NONE)
find docroot/sites/default/files -name "*.php" -type f
Expected:
settings.phpshould be 444 or 644 (not writable)files/directory should not contain any.phpfiles.htaccessshould exist in files directory
5. Check for Exposed Sensitive Files
# These should NOT be web-accessible
ls -la .env 2>/dev/null
ls -la .git 2>/dev/null
ls -la composer.json
ls -la web/.htaccess
Verify .htaccess or server config blocks access to:
.envfiles.gitdirectorycomposer.json/composer.lockvendor/directoryconfig/sync/directory
6. Review Custom Code for Common Vulnerabilities
Scan custom modules for security issues:
# Find potential SQL injection (string concatenation in queries)
grep -r "db_query.*\$" docroot/modules/custom/
grep -r '->query.*".*\$' docroot/modules/custom/
# Find potential XSS (raw output without sanitization)
grep -r "#markup.*\$" docroot/modules/custom/
grep -r "Markup::create.*\$" docroot/modules/custom/
# Find hardcoded credentials
grep -ri "password\s*=" docroot/modules/custom/
grep -ri "api_key\s*=" docroot/modules/custom/
grep -ri "secret" docroot/modules/custom/
# Find static service calls (testability/security smell)
grep -r "\\Drupal::" docroot/modules/custom/src/
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 · 191 lines · 13 tokens per session scan A 88f544b40d38
security-audit is a command published in the GitHub repository edutrul/drupal-ai (71 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 1,142 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-30.
Other commands, from other repositories
build
Run full verification pipeline.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
camera-ready
Convert an accepted anonymous-submission LaTeX paper (AAAI/AIES/ACM-style) to camera-ready and implement the accepted reviews. Use when a paper is accepted with no rebuttal and you need to de-anonymize, add copyright, turn on section numbering, implement each reviewer's minor revisions, optionally move proofs to a…
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
generate-rules
Generate development rules and standards into RULES.md.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.