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/performance-auditnpx skills add trebormc/drupal-ai-agents --skill performance-auditgit 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/performance-audit)<a href="https://agentmods.dev/skills/trebormc/drupal-ai-agents/performance-audit"><img src="https://agentmods.dev/badge/skills/trebormc/drupal-ai-agents/performance-audit.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.00058 | $0.01309 |
| Opus 5 | $0.00029 | $0.00655 |
| Sonnet 5 | $0.00012 | $0.00262 |
| Haiku 4.5 | $0.00006 | $0.00131 |
Grade A, and why
performance-audit scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
# NOT functional testing; functional testing still uses Playwright, never curl): How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Audit
Diagnostic Commands
# Enabled modules count — over ~100 on a simple site suggests module bloat
ssh web drush pm:list --status=enabled --format=list | wc -l
# Recent PHP errors — repeated warnings/notices on every request cost performance
ssh web drush watchdog:show --type=php --count=20
# Slow queries counter — a value > 0 that grows on reload means slow SQL to investigate
ssh web drush sqlq "SHOW STATUS LIKE 'Slow_queries'"
For function-level profiling, use the xdebug-profiling skill.
Baseline Measurement (do this BEFORE and AFTER any change)
# Page timing from inside the web container (timing measurement only — this is
# NOT functional testing; functional testing still uses Playwright, never curl):
ssh web curl -s -o /dev/null -w "first: %{time_total}s\n" http://localhost/PATH
ssh web curl -s -o /dev/null -w "second (warm cache): %{time_total}s\n" http://localhost/PATH
Record both numbers. After your fix, re-run and compare — if there is no measurable improvement, the bottleneck is elsewhere.
How to Detect N+1 Queries
- Profile the slow page with the xdebug-profiling skill (profile mode).
- In the analyzer output, look for entity load / query functions with a very high call COUNT (e.g.
Drupal\Core\Entity\...::loadcalled 200 times). - Find the loop in the code calling
load()per item and replace withloadMultiple(). - Alternative: if the devel/webprofiler module is installed, enable its DB query log and look for many near-identical queries.
Caching Strategy
Cache Tags (What to invalidate)
$build['#cache']['tags'] = ['node:123', 'node_list'];
// Custom tags
$build['#cache']['tags'] = Cache::mergeTags(
$entity->getCacheTags(),
['mymodule:custom_list']
);
Cache Contexts (When to vary)
$build['#cache']['contexts'] = [
'user.permissions',
'user.roles:authenticated',
'url.query_args',
'languages:language_content',
];
Cache Max-Age
$build['#cache']['max-age'] = 3600; // 1 hour
$build['#cache']['max-age'] = 0; // Never cache (use sparingly!)
$build['#cache']['max-age'] = Cache::PERMANENT; // Until invalidated
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.
- 4d ago First seen · 173 lines · 58 tokens per session scan A c7ad9479f50e
performance-audit is a skill published in the GitHub repository trebormc/drupal-ai-agents (10 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 58 tokens to every session and 1,309 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…