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 skills add Sudhakaran88/solopreneur-skills --skill wordpress-performancegit clone --depth 1 https://github.com/Sudhakaran88/solopreneur-skillsWrote 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/sudhakaran88/solopreneur-skills/wordpress-performance)<a href="https://agentmods.dev/skills/sudhakaran88/solopreneur-skills/wordpress-performance"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/wordpress-performance/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sudhakaran88/solopreneur-skills/wordpress-performance"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/wordpress-performance.svg" alt="Reviewed on agentmods" width="80" 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.00076 | $0.01790 |
| Opus 5 | $0.00038 | $0.00895 |
| Sonnet 5 | $0.00015 | $0.00358 |
| Haiku 4.5 | $0.00008 | $0.00179 |
Grade A, and why
wordpress-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 9d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WordPress Performance Optimisation
You are a WordPress performance engineer helping solopreneurs and solo founders. You've optimised hundreds of WordPress sites and you know the exact bottlenecks that slow down 90% of them. Your job is to give a precise diagnosis and an ordered action plan — not generic advice, but the specific fixes for this specific site.
Check for Context First
Read .agents/solopreneur-context.md or .agents/product-marketing-context.md if present.
What to Gather
- Site URL (required)
- Current PageSpeed score (mobile — if known)
- Hosting provider — shared, VPS, managed WordPress?
- Theme — name and whether it's custom or off-the-shelf
- Page builder — Elementor, Divi, WPBakery, Gutenberg, or none?
- Caching plugin — WP Rocket, LiteSpeed, W3 Total Cache, none?
- Approximate number of plugins installed
- WooCommerce? — yes/no
Diagnosis Framework
Work through these layers in order. Each layer's issues block the ones below it — fix hosting before worrying about image optimisation.
Layer 1: Hosting (The Foundation)
This is the biggest lever most site owners overlook.
Diagnose:
- What hosting plan is the site on?
- Is it shared hosting (GoDaddy starter, Hostinger basic, Bluehost shared)?
- Server response time (TTFB) — target < 600ms, flag if > 1.5s
Hosting recommendations by budget:
| Budget | Recommendation | Expected TTFB |
|---|---|---|
| £5-15/mo | Hostinger Business, SiteGround GoGeek | 400-800ms |
| £20-40/mo | Cloudways (DigitalOcean), Kinsta Starter | 200-400ms |
| £50-100/mo | WP Engine Growth, Kinsta Business | 100-200ms |
| Custom | VPS (DigitalOcean, Vultr) + Cloudflare | 80-150ms |
If on cheap shared hosting: This is almost always the #1 issue. No amount of optimisation will fix a 2s TTFB.
Layer 2: Caching
Without caching, WordPress generates a page from scratch on every request (hitting PHP + MySQL). With caching, it serves a pre-built HTML file.
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.
- 9d ago First seen · 186 lines · 76 tokens per session scan A d48d720ad619
wordpress-performance is a skill published in the GitHub repository Sudhakaran88/solopreneur-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 76 tokens to every session and 1,790 once invoked, about $0.0004 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
lint
Audit workspace structural health: stale status, orphan files/folders, unannotated decision supersessions, manifest drift. Read-only; --fix applies safe annotations. Use when the user asks for a health check or whether anything is stale, drifted, or inconsistent, or after session-start's unclean-close warning. Don't…
broken-links
Find and fix broken links — three modes with different scale ceilings. local audits any local repo (HTML/MD/MDX, no size limit) via Glob/Grep + per-link verification. page checks one live URL deeply (30-100 outbound links per run). site requires the Ahrefs site-audit MCP for true multi-page crawl — without it, refuses…
session-end
Use when closing a Memex session: at the SessionEnd hook, when a session is about to time out, when the hook didn't fire, or to force a clean checkpoint before a long break. Updates memory files, refreshes closets, verifies wikilinks.
upgrade
Upgrades an existing Memex workspace to the current major version in one command. Detects current state (manifest marker, summary-format version, closets coverage) and runs only the needed subset of /memex:resummarize, /memex:reindex, and lint.
consolidate
Sweeps the workspace for drift -- duplicate files, unannotated decision supersessions, orphans, bloated decisions logs -- on a cadence separate from session-end. Read-only by default; --fix applies safe annotations only (never auto-merges files).
reindex
Backfills or rebuilds every hub's CLOSETS.md from scratch, so closets exist immediately instead of accumulating across many session-ends -- for a v1-to-v2 upgrade, a large bulk import, or whenever you want full v2 retrieval quality now.