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 seogit 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)<a href="https://agentmods.dev/skills/kabde/seo-skills/seo"><img src="https://agentmods.dev/badge/skills/kabde/seo-skills/seo/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"><img src="https://agentmods.dev/badge/skills/kabde/seo-skills/seo.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.00063 | $0.01388 |
| Opus 5 | $0.00032 | $0.00694 |
| Sonnet 5 | $0.00013 | $0.00278 |
| Haiku 4.5 | $0.00006 | $0.00139 |
Grade A, and why
seo 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Blogger Toolkit - Orchestrator
Invocation: /seo <command> <argument>
Toolkit SEO complet pour blogueurs WordPress. 15 skills couvrant le cycle de vie complet du contenu : recherche, planification, redaction, audit, optimisation IA, publication.
Quick Reference
| Command | What it does |
|---|---|
/seo-audit <url> |
Full website audit with parallel subagents |
/seo-wordpress <url> |
WordPress blog SEO audit via REST API |
/seo-wp-strategy <url> |
Content strategy, editorial calendar, gap analysis |
/seo-write-article <keyword> |
Write a full SEO + GEO optimized article |
/seo-outline-article <keyword> |
Plan article structure (H1-H3, key points) |
/seo-wordpress-publish <file> |
Publish article to WordPress via REST API |
/seo-brand-voice |
Define or check brand voice & editorial tone |
/seo-cluster <seed-keyword> |
Topic clusters: pillar + secondary articles |
/seo-content <url> |
E-E-A-T and content quality analysis |
/seo-page <url> |
Deep single-page SEO analysis |
/seo-schema <url> |
Detect, validate, generate Schema.org markup |
/seo-geo <url> |
AI search / GEO optimization (ChatGPT, Perplexity) |
/seo-images <url> |
Image optimization analysis |
/seo-technical <url> |
Technical SEO audit (CWV, mobile, crawlers) |
Blogger Workflow
The recommended workflow for bloggers:
1. /seo-wordpress <url> → Audit existing content
2. /seo-cluster <keyword> → Plan pillar + secondary articles
3. /seo-wp-strategy <url> → Generate 12-week editorial calendar
4. /seo-brand-voice → Define writing tone & guidelines
5. /seo-outline-article <keyword> → Plan article structure
6. /seo-write-article <keyword> → Write full article (SEO + GEO)
7. /seo-content <draft> → Audit E-E-A-T before publish
8. /seo-schema <url> → Add BlogPosting schema
9. /seo-geo <url> → Optimize for AI citations
10. /seo-wordpress-publish <file> → Publish to WordPress
What ships with it
13 files 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.
- LICENSE.txt 152 B
- references/backlink-quality.md 3.4 KB
- references/cwv-thresholds.md 5.0 KB
- references/eeat-framework.md 7.3 KB
- references/free-backlink-sources.md 5.3 KB
- references/local-schema-types.md 9.1 KB
- references/local-seo-signals.md 8.4 KB
- references/maps-api-endpoints.md 5.9 KB
- references/maps-free-apis.md 6.0 KB
- references/maps-gbp-checklist.md 5.9 KB
- references/maps-geo-grid.md 4.3 KB
- references/quality-gates.md 5.1 KB
- references/schema-types.md 6.1 KB
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 · 127 lines · 63 tokens per session scan A 8f754bcfa972
seo is a skill published in the GitHub repository kabde/seo-skills (11 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 1,388 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…