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 kabde/seo-skills --skill seo-wordpress-publishgit clone --depth 1 https://github.com/kabde/seo-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/kabde/seo-skills/seo-wordpress-publish)<a href="https://agentmods.dev/skills/kabde/seo-skills/seo-wordpress-publish"><img src="https://agentmods.dev/badge/skills/kabde/seo-skills/seo-wordpress-publish/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/kabde/seo-skills/seo-wordpress-publish"><img src="https://agentmods.dev/badge/skills/kabde/seo-skills/seo-wordpress-publish.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.00068 | $0.01445 |
| Opus 5 | $0.00034 | $0.00723 |
| Sonnet 5 | $0.00014 | $0.00289 |
| Haiku 4.5 | $0.00007 | $0.00145 |
Grade A, and why
seo-wordpress-publish 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 11d 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.
WordPress Publish
Publish articles to WordPress via the REST API from Markdown files or direct content.
Invocation
/seo-wordpress-publish <file.md>
/seo-wordpress-publish <file.md> --site https://example.com --status publish
/seo-wordpress-publish <file.md> --status scheduled --date 2026-05-01T09:00:00
Prerequisites
WordPress credentials must be configured in ~/.config/claude-seo/wordpress.json:
{
"site_url": "https://your-site.com",
"username": "your-username",
"application_password": "xxxx xxxx xxxx xxxx"
}
Generate an Application Password in WordPress: Users > Profile > Application Passwords.
Workflow
- Read Markdown file -- Parse frontmatter (YAML) and body content
- Convert Markdown to HTML -- Preserve headings, lists, code blocks, images
- Authenticate -- Connect via Application Password (Basic Auth over HTTPS)
- Create or update post -- POST to
/wp/v2/posts(or PUT for updates) - Set categories and tags -- Look up by name, create if they don't exist
- Set featured image -- Upload via
/wp/v2/mediaiffeatured_imagepath given - Set SEO meta -- Auto-configure Yoast or RankMath title + description via REST API
- Set status --
draft(default),publish, orfuture(scheduled) - Return post URL and ID -- Confirm publication with direct link
Supported Frontmatter Fields
---
title: "Mon article SEO optimise"
description: "Meta description pour les moteurs de recherche (max 160 chars)"
category: "Marketing Digital"
tags:
- SEO
- WordPress
- Content Marketing
featured_image: "./images/hero.jpg"
status: draft # draft | publish | future
date: "2026-05-01T09:00:00" # Required if status is 'future'
slug: "mon-article-seo"
---
| Field | Required | Default | Description |
|---|---|---|---|
title |
Yes | -- | Post title (H1) |
description |
Recommended | -- | Meta description for SEO plugins |
category |
Recommended | Uncategorized | Primary category name |
tags |
Optional | [] | List of tag names |
featured_image |
Recommended | -- | Path to image file (local or URL) |
status |
Optional | draft | Post status |
date |
Optional | now | Publish date (ISO 8601), required for scheduled |
slug |
Optional | auto | URL slug |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 153 lines · 68 tokens per session scan A e72388ab9450
seo-wordpress-publish is a skill published in the GitHub repository kabde/seo-skills (11 stars, last pushed 4mo ago), licensed MIT. It adds 68 tokens to every session and 1,445 once invoked, about $0.0003 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…