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-content-metadatagit 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-content-metadata)<a href="https://agentmods.dev/skills/lonsdale201/wp-agent-skills/lw-seo-content-metadata"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/lw-seo-content-metadata/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-content-metadata"><img src="https://agentmods.dev/badge/skills/lonsdale201/wp-agent-skills/lw-seo-content-metadata.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.00091 | $0.01804 |
| Opus 5.5 | $0.00036 | $0.00722 |
| Sonnet 5.5 | $0.00018 | $0.00361 |
| Haiku 4.5 | $0.00009 | $0.00180 |
Grade A, and why
lw-seo-content-metadata 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LW SEO content metadata
Use LW SEO's public options, metadata helpers, and filters when another plugin owns the content model. Do not duplicate the plugin's head tags or write serialized option arrays from request data.
Binding contract
| Contract | LW SEO 1.7.4 |
|---|---|
| WordPress | 6.6 or newer |
| PHP | 8.2 or newer |
| Main option | lw_seo_options |
| Post and term meta prefix | _lw_seo_ |
| Settings screen | LW Plugins -> SEO |
| Public REST namespace | lw-seo/v1 |
| Ability namespace | lw-seo/* |
The React settings screen depends on WordPress 6.6's react-jsx-runtime. Treat the declared minimum as a runtime requirement.
Store per-object values through the plugin contract
The supported post and term fields are:
| Field | Stored key | Value |
|---|---|---|
| SEO title | _lw_seo_title |
template-aware string |
| Description | _lw_seo_description |
plain text |
| Robots | _lw_seo_noindex, _lw_seo_nofollow |
'1' or absent |
| Canonical | _lw_seo_canonical |
absolute URL |
| Social | _lw_seo_og_title, _lw_seo_og_description, _lw_seo_og_image |
plain text or image URL |
| Content Signals | _lw_seo_search, _lw_seo_ai_input, _lw_seo_ai_train |
yes, no, or absent |
| Markdown override | _lw_seo_markdown_content |
raw override; unfiltered_html required |
For code running with LW SEO active, prefer its helpers:
use LightweightPlugins\SEO\Options;
Options::set_post_meta( $post_id, 'title', 'A complete title %%sep%% %%sitename%%' );
Options::set_post_meta( $post_id, 'description', 'A concise search description.' );
$title = (string) Options::get_post_meta( $post_id, 'title' );
Options::set_post_meta() and set_term_meta() delete an empty value. Do not call them until LW SEO has loaded, and do not make a companion plugin depend on these internal classes when ordinary WordPress metadata plus public filters is enough.
For agent or remote writes, use lw-seo/set-meta; it sanitizes known fields, rejects unknown fields, enforces object-level editing, and applies the unfiltered_html gate to the Markdown override.
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 · 171 lines · 91 tokens per session scan A 2ab9e4b75e81
lw-seo-content-metadata is a skill published in the GitHub repository Lonsdale201/wp-agent-skills (24 stars, last pushed 4d ago), licensed MIT. It adds 91 tokens to every session and 1,804 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"…