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/dr-robert-li/cowork-wordpress-expert/performancenpx skills add dr-robert-li/cowork-wordpress-expert --skill performancegit clone --depth 1 https://github.com/dr-robert-li/cowork-wordpress-expertWrote 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/dr-robert-li/cowork-wordpress-expert/performance)<a href="https://agentmods.dev/skills/dr-robert-li/cowork-wordpress-expert/performance"><img src="https://agentmods.dev/badge/skills/dr-robert-li/cowork-wordpress-expert/performance.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.1 | $0.00036 | $0.00823 |
| Opus 5 | $0.00018 | $0.00411 |
| Sonnet 5 | $0.00007 | $0.00165 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
performance 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 6d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain 3: Performance Analysis
3.1 Database Performance
- Identify N+1 query patterns (queries inside loops)
- Flag
meta_querywithout proper indexing - Detect unnecessary
LIKE '%value%'queries (leading wildcard prevents index use) - Check for missing indexes on custom tables
- Identify excessive
wp_optionsautoloading (total autoloaded data size) - Review transient usage — orphaned or never-expiring transients
- Detect
SELECT *where specific columns would suffice - Flag
ORDER BY RAND()on large datasets - Check post revision accumulation and recommend limits
- Review
wp_postmetatable bloat
3.2 PHP Performance
- Identify expensive operations in
init,wp_loaded, oradmin_inithooks that should run conditionally - Detect heavy computation on every page load vs lazy/on-demand execution
- Flag blocking HTTP API calls without timeouts
- Identify missing object caching for repeated expensive operations
- Check for excessive use of
get_option()on non-autoloaded options (each triggers a DB query) - Detect memory-intensive operations (loading all posts, large arrays in memory)
- Review cron jobs for efficiency and proper scheduling
- Identify duplicate plugin functionality (multiple SEO plugins, multiple caching layers)
3.3 Frontend Performance
- Audit render-blocking CSS and JavaScript
- Check proper use of
wp_enqueue_script()/wp_enqueue_style()(not hardcoded in templates) - Verify scripts load in footer where possible (
in_footerparameter) - Identify scripts/styles loaded globally that should be conditional
- Check for proper async/defer attributes
- Review image optimization (WebP support, proper sizing, lazy loading)
- Identify excessive DOM size from page builder bloat
- Check for unused CSS/JS being loaded
- Verify proper use of WordPress asset dependency system
- Core Web Vitals impact assessment (LCP, FID/INP, CLS)
3.4 Caching Analysis
- Page caching configuration and effectiveness
- Object caching (Redis/Memcached) configuration
- Browser caching headers (Cache-Control, Expires, ETag)
- CDN configuration and cache hit rates
- Fragment caching for dynamic content areas
- Transient API usage patterns
- OPcache configuration for PHP
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.
- 6d ago First seen · 107 lines · 36 tokens per session scan A 5338af26e419
performance is a skill published in the GitHub repository dr-robert-li/cowork-wordpress-expert (28 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 823 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…