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 Lonsdale201/wp-agent-skills --skill lw-seo-automation-compatibilitygit clone --depth 1 https://github.com/Lonsdale201/wp-agent-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/lonsdale201/wp-agent-skills/lw-seo-automation-compatibility)<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/lw-seo-automation-compatibility"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/lw-seo-automation-compatibility/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/lonsdale201/wp-agent-skills/lw-seo-automation-compatibility"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/lw-seo-automation-compatibility.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.00107 | $0.01990 |
| Opus 5.5 | $0.00043 | $0.00796 |
| Sonnet 5.5 | $0.00021 | $0.00398 |
| Haiku 4.5 | $0.00011 | $0.00199 |
Grade A, and why
lw-seo-automation-compatibility 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 28d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LW SEO automation and compatibility
Choose the interface by audience. WP-CLI and abilities are administrative surfaces. The lw-seo/v1 routes are public read-only headless output and must never be treated as an authorization layer.
Verified compatibility matrix
| Plugin | Verified version | Result |
|---|---|---|
| LW SEO | 1.7.4 | active release package; 196 shipped non-vendor files matched public source after line-ending normalization |
| LW Cookie | 1.8.3 | frontend banner and SEO tags coexist; SEO did not set a response cookie |
| LW LMS | 2.0.1 | headless course and lesson excluded from sitemap and llms collectors |
| LW Site Manager | 1.5.1 | all five SEO abilities registered, MCP-public, and present in discovery |
The live smoke ran on WordPress 7.1.2 and PHP 8.3.30. Recheck behavior after any plugin version changes.
Use WP-CLI for deployment and operations
The main command groups are:
wp lw-seo option get|set|list|reset
wp lw-seo sitemap info|flush
wp lw-seo llms info|preview|flush
wp lw-seo robots preview
wp lw-seo crawlers list
wp lw-seo redirect list|add|delete|import|export
wp lw-seo migrate rankmath|yoast
option set uses the settings sanitizer. Boolean values accept explicit true/false forms; map options accept JSON objects. A map write replaces the whole map, while a dot path updates one member:
wp lw-seo option set sitemap_post_types.event true
wp lw-seo option set llms_txt_post_types.internal_doc false
Read current values before mutation and read them back afterward. option reset, redirect deletes, imports, and migrations require an explicit change window and backup.
Use the five Site Manager abilities
| Ability | Permission | Purpose |
|---|---|---|
lw-seo/get-meta |
edit_posts plus target read access |
read post or term SEO fields |
lw-seo/set-meta |
edit_posts plus target edit access |
update supplied fields only |
lw-seo/get-content-signals |
edit_posts plus target read access |
resolved signal map |
lw-seo/get-markdown |
edit_posts plus target read access |
rendered Markdown |
lw-seo/get-options |
manage_options |
global merged options |
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.
- 28d ago First seen · 153 lines · 107 tokens per session scan A ece07e0f1b0b
lw-seo-automation-compatibility is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (24 stars, last pushed 4d ago), licensed MIT. It adds 107 tokens to every session and 1,990 once invoked, about $0.0004 per session on Opus 5.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-09-27.
Other skills, from other repositories
wp-readme-optimizer
Reviews and rewrites WordPress.org plugin readme.txt files for maximum quality. Use this skill whenever a user pastes, uploads, or references a WordPress plugin readme.txt, or asks to improve, audit, review, score, or optimize a plugin's WordPress.org listing page. Also trigger when the user says things like "make my…
astro-seo
Audits and improves SEO for Astro sites. Use when the user asks to audit, set up, or improve SEO on an Astro site, or mentions head metadata, structured data, JSON-LD, sitemaps, IndexNow, Open Graph images, schema endpoints, NLWeb, hreflang, or search engine indexing in an Astro project. Produces drop-in code routed…
static-seo
Audits and improves SEO for static HTML sites. Use when the user asks to audit, set up, or improve SEO on a static site (Hugo, Jekyll, 11ty, Gatsby, Next.js static export, hand-rolled HTML, or wp-static-clone output), or mentions head metadata, structured data, JSON-LD, sitemaps, IndexNow, Open Graph images, schema…
readability-check
Runs a readability audit on a blog post draft or other multi-paragraph prose, calibrated for readers who read English as a second language. Checks ten categories — overall structure and topic order, paragraph structure, opening paragraph strength, tiered sentence length, passive voice, difficult words, filler and…
wp-static-clone
Clones a live WordPress (or other CMS-driven) site into a static HTML site deployable on any static host (Cloudflare Pages, Netlify, Vercel, S3+CloudFront, plain Apache/nginx). Use when the user wants to "scrape", "freeze", "archive", "static-ify", or "move to [host]" a WordPress site, or asks to turn a sitemap into…
content-seo
Audits a blog post draft or page copy for content-level SEO: search intent fit, focus keyphrase placement, E-E-A-T signals (experience, expertise, authoritativeness, trustworthiness), helpfulness and originality, content freshness, and internal linking. Use when the user asks "will this rank", "SEO check this post"…