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-outline-articlegit 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-outline-article)<a href="https://agentmods.dev/skills/kabde/seo-skills/seo-outline-article"><img src="https://agentmods.dev/badge/skills/kabde/seo-skills/seo-outline-article/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-outline-article"><img src="https://agentmods.dev/badge/skills/kabde/seo-skills/seo-outline-article.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.00065 | $0.01685 |
| Opus 5 | $0.00032 | $0.00843 |
| Sonnet 5 | $0.00013 | $0.00337 |
| Haiku 4.5 | $0.00006 | $0.00169 |
Grade A, and why
seo-outline-article 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Article Outline Planner
Invocation
/seo-outline-article <keyword>
Optional flags:
--type <type>: standard or pillar (default: standard)--template <template>: how-to, listicle, guide, comparison, case-study, explainer (default: auto-detect from SERP)--cluster <name>: load cluster plan for internal link suggestions
Prerequisites
- WebSearch access: required for SERP analysis and competitor research
- Cluster context (optional): pass
--clusterto integrate with an existing topic cluster
Workflow
Step 1: Keyword Research
Use WebSearch to collect:
- Top 10 Google SERP results for the target keyword
- People Also Ask (PAA) questions (5-8 questions)
- Related searches and long-tail keyword variations
- Featured snippet format currently ranking (paragraph, list, table)
- Search intent classification (informational, commercial, transactional, navigational)
Step 2: Analyze Competitor Outlines
For each top 5 ranking page:
- Extract heading structure (H1, H2, H3)
- Estimate word count per section
- Note content formats used (lists, tables, images, videos)
- Identify unique angles or data points
- Record external sources cited
Build a competitor heading matrix:
| Heading Topic | Page 1 | Page 2 | Page 3 | Page 4 | Page 5 |
|----------------------|--------|--------|--------|--------|--------|
| Definition/What Is | Y | Y | Y | Y | Y |
| How It Works | Y | Y | N | Y | N |
| Benefits | Y | N | Y | Y | Y |
| [Topic-specific] | N | Y | N | N | N |
Step 3: Identify Content Gaps
From the competitor analysis, find:
- Topics all competitors cover (must include - table stakes)
- Topics most competitors miss (opportunity for differentiation)
- Questions from PAA not answered by top results
- Depth gaps: sections competitors cover superficially
- Format gaps: content types competitors don't use (tables, comparisons, calculators)
- Freshness gaps: outdated data or stats in competitor articles
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 · 204 lines · 65 tokens per session scan A 195b8cc30950
seo-outline-article is a skill published in the GitHub repository kabde/seo-skills (11 stars, last pushed 4mo ago), licensed MIT. It adds 65 tokens to every session and 1,685 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…