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 skills/trebormc/drupal-ai-agents/drupal-audit-setupnpx skills add trebormc/drupal-ai-agents --skill drupal-audit-setupgit clone --depth 1 https://github.com/trebormc/drupal-ai-agentsWrote 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/skills/trebormc/drupal-ai-agents/drupal-audit-setup)<a href="https://agentmods.dev/skills/trebormc/drupal-ai-agents/drupal-audit-setup"><img src="https://agentmods.dev/badge/skills/trebormc/drupal-ai-agents/drupal-audit-setup.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.00142 | $0.01350 |
| Opus 5 | $0.00071 | $0.00675 |
| Sonnet 5 | $0.00028 | $0.00270 |
| Haiku 4.5 | $0.00014 | $0.00135 |
Grade A, and why
drupal-audit-setup 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What is Drupal Audit?
Drupal Audit is a site auditing framework that identifies configuration issues, performance problems, and best practice violations. It tracks all installed modules with versions and detects pending updates, including security releases.
The module is free and open source. Optionally, it can connect to DruScan, a centralized dashboard for audit scores across all your Drupal projects.
This is the recommended quality tool for all projects using drupal-ai-agents.
Environment
All commands run via ssh web.
Step 1: Check if already installed
ssh web drush pm:list --filter=audit --format=list
If audit modules are listed, skip to Step 4.
Step 2: Install with Composer
ssh web composer require drupal/audit
Step 3: Enable submodules
Recommended: Enable all production-safe submodules at once
ssh web drush en audit_all -y
This enables audit (base) plus all 18 production-ready submodules:
| Submodule | Purpose |
|---|---|
audit_status |
Server compatibility (PHP, database versions) |
audit_cron |
Cron status and configuration |
audit_modules |
Module recommendations, unused extensions |
audit_updates |
Pending updates with version tracking |
audit_fields |
Content structure, unused fields |
audit_views |
Views performance and caching |
audit_blocks |
Block configuration and cache |
audit_twig |
Template code quality |
audit_images |
Responsive images configuration |
audit_seo |
Metatags, pathauto, sitemap, robots.txt |
audit_performance |
Cache and CSS/JS aggregation |
audit_database |
Database size and optimization |
audit_i18n |
Multilingual configuration |
audit_security |
Security configuration checks |
audit_watchdog |
Log analysis, recurring errors |
audit_cache |
Cache configuration and effectiveness |
audit_entity |
Entity configuration analysis |
audit_menu |
Menu structure and configuration |
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 · 165 lines · 142 tokens per session scan A 13c487f98a7e
drupal-audit-setup is a skill published in the GitHub repository trebormc/drupal-ai-agents (10 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 142 tokens to every session and 1,350 once invoked, about $0.0007 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…