performance-check

A command for checking how a Drupal website is configured for speed, including page caching, browser-file aggregation, cache backends, and custom module code.

In plain words
What is it for?
Use it for a whole-site performance review or to focus the analysis on one module, then identify caching changes worth making.
Why use it?
It helps find settings or code that may cause slow page responses or prevent Drupal from reusing stored results.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/edutrul/drupal-ai/performance-check
Clone the repo
git clone --depth 1 https://github.com/edutrul/drupal-ai

Made for: Claude Code.

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,536 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00010 $0.01536
Opus 5 $0.00005 $0.00768
Sonnet 5 $0.00002 $0.00307
Haiku 4.5 $0.00001 $0.00154

Measured 2d ago against content hash d68dcc73f343, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

performance-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 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.

.claude/commands/performance-check.md · 226 lines

How it starts

The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Drupal Performance Check

Analyze site performance configuration and identify optimization opportunities.

Usage: /performance-check [module_path]

If a module path is provided, focus analysis on that module's code. Otherwise, check site-wide performance settings and scan all custom modules.

Path note: Commands below use docroot/ as the web root. Adjust to match your project layout (common alternatives: web/, html/). Similarly, docroot/modules/custom/ assumes the standard custom modules location — update if yours differs.

Performance Analysis Steps

1. Check Caching Configuration

# Page cache
drush config:get system.performance cache.page.max_age

# CSS/JS aggregation
drush config:get system.performance css.preprocess
drush config:get system.performance js.preprocess

# Twig cache (should NOT be disabled in production)
drush php:eval "var_dump(\$settings['cache']['bins']['render'] ?? 'default');"

Production should have:

  • cache.page.max_age > 0 (e.g., 3600 for 1 hour)
  • css.preprocess = true
  • js.preprocess = true
  • No cache bins disabled

2. Check Cache Backends

# What cache backends are configured?
drush php:eval "print_r(\$settings['cache']['default'] ?? 'database');"

# List all cache bins
drush cache:list

Recommendations:

  • Use Redis or Memcache for production (not database)
  • Consider separate backends for different cache bins

3. Review BigPipe Status

drush pm:list --filter=big_pipe
drush config:get big_pipe.settings

BigPipe should be enabled for authenticated user performance.

4. Check Database Performance

# Show slow query log (if enabled)
drush watchdog:show --filter="type=php" --severity=warning --count=20

# Check database size
drush sql:query "SELECT table_name, round(((data_length + index_length) / 1024 / 1024), 2) AS 'Size (MB)' FROM information_schema.tables WHERE table_schema = DATABASE() ORDER BY (data_length + index_length) DESC LIMIT 10;"

Read the full file on GitHub · 226 lines

Changes

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.

  1. 2d ago First seen · 226 lines · 10 tokens per session scan A d68dcc73f343

Subscribe to this mod's changes

performance-check is a command published in the GitHub repository edutrul/drupal-ai (71 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 1,536 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.