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 Jeffallan/writing-with-agents --skill seo-writergit clone --depth 1 https://github.com/Jeffallan/writing-with-agentsWrote 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/jeffallan/writing-with-agents/seo-writer)<a href="https://agentmods.dev/skills/jeffallan/writing-with-agents/seo-writer"><img src="https://agentmods.dev/badge/skills/jeffallan/writing-with-agents/seo-writer/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/jeffallan/writing-with-agents/seo-writer"><img src="https://agentmods.dev/badge/skills/jeffallan/writing-with-agents/seo-writer.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.00033 | $0.01812 |
| Opus 5 | $0.00016 | $0.00906 |
| Sonnet 5 | $0.00007 | $0.00362 |
| Haiku 4.5 | $0.00003 | $0.00181 |
Grade A, and why
seo-writer 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role Definition
The SEO Writer is the search optimization integration specialist. This is a cross-cutting skill that provides SEO guidance during the Architect (planning), Carpenter (execution), and Judge (validation) phases. It does not replace those phases -- it augments them with search-aware decisions.
Lead: AI analyzes search intent, maps keywords, and runs SEO validation. Support: Human confirms keyword targets, approves heading architecture, and decides trade-offs between readability and optimization.
The SEO Writer understands search intent classification, keyword-to-heading mapping, heading architecture for crawlability, featured snippet targeting patterns, and E-E-A-T signals. It applies these across the writing workflow rather than as an afterthought bolted onto a finished draft.
When to Use This Skill
- When the content goal includes organic search visibility
- When you need to analyze search intent before planning content structure
- When mapping keywords to headings during the Architect phase
- When targeting featured snippets or People Also Ask boxes
- When integrating keywords naturally during the Carpenter phase
- When writing or reviewing meta elements (title tags, meta descriptions, URL slugs)
- When running SEO validation during the Judge phase
- When auditing existing content for on-page SEO gaps
- When consolidating multiple thin pages into a single authoritative resource
- When a published article is underperforming in search and needs diagnostic analysis
- When planning internal linking strategy across a content cluster
Core Workflow
-
Analyze Search Intent and SERP Landscape -- Classify the target query as informational, navigational, commercial, or transactional. Run the SERP analysis checklist to understand what content format dominates, what subtopics are table stakes, and where opportunity gaps exist. See
references/search-intent-analysis.md. -
Architect Phase: Map Keywords to Structure -- During the Architect phase, map primary and secondary keywords to specific headings. Plan which headings target People Also Ask questions. Identify featured snippet opportunities and assign snippet formats (paragraph, list, table) to specific sections. See
references/keyword-mapping.md.
What ships with it
5 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.
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 · 128 lines · 33 tokens per session scan A 3dbfe1044fbf
seo-writer is a skill published in the GitHub repository Jeffallan/writing-with-agents (31 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 1,812 once invoked, about $0.0002 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…