What is seo-content-factory?

A workflow for writing and publishing search-focused blog articles through an SEO content server. It requires items such as an FAQ, a cover image, internal links, and validation.

Use it when creating one or more blog articles for a connected website, including topic selection, related-article links, FAQ sections, images, and publication.

It prevents duplicate articles and incomplete publishing by checking existing content and enforcing required page elements.

seo-content-factory — Skill for Claude Code by skiddgoddamn

Install

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.

Any agent

npx skills add skiddgoddamn/seo-factory-mcp --skill seo-content-factory

Clone the repo

git clone --depth 1 https://github.com/skiddgoddamn/seo-factory-mcp

Made for: Claude Code.

Or install seo-factory, the plugin that ships this one along with the rest of its 2 skills, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/skiddgoddamn/seo-factory-mcp/seo-content-factory/github.svg)](https://agentmods.dev/skills/skiddgoddamn/seo-factory-mcp/seo-content-factory)

Your own site

<a href="https://agentmods.dev/skills/skiddgoddamn/seo-factory-mcp/seo-content-factory"><img src="https://agentmods.dev/badge/skills/skiddgoddamn/seo-factory-mcp/seo-content-factory/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/skiddgoddamn/seo-factory-mcp/seo-content-factory"><img src="https://agentmods.dev/badge/skills/skiddgoddamn/seo-factory-mcp/seo-content-factory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 130 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,090 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00130	$0.01090
Opus 5	$0.00065	$0.00545
Sonnet 5	$0.00026	$0.00218
Haiku 4.5	$0.00013	$0.00109

Measured 11d ago against content hash e21e7d23f9cd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

seo-content-factory 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.

skills/seo-content-factory/SKILL.md · 56 lines

How it starts

The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SEO контент-фабрика

Публикация статей на любой сайт, подключённый через add_site (MCP seo-factory). Цель — не «текст ради текста», а страница, которая собирает поисковый трафик: уникальный смысловой блок, FAQ-разметка, внутренние ссылки.

Рабочий процесс (делай по шагам)

Уточни вход. Тема/кластер (или готовый вердикт new из match_queries), сайт (алиас; по умолчанию дефолтный), сколько статей. Если сайтов нет — setup и проведи пользователя по онбордингу.
Проверь дубли и собери перелинковку. list_articles с query по ключевым словам темы — нет ли уже такой статьи (есть → предложи дожать через update_article, а не плодить дубль). Затем suggest_links по 1-2 близким статьям — получи готовые markdown-сниппеты для «Смотри также» в теле.
Напиши текст по правилам reference/content-rules.md. Обязательно:
- начни content со строки # Заголовок (title отдельно НЕ передавай);
- первый абзац ≤160 символов (станет meta description);
- секция ## FAQ с ≥2 парами ### Вопрос? → ответ (активирует FAQPage-разметку);
- ≥2 внутренние ссылки на близкие статьи (сниппеты из шага 2);
- обложка: upload_image → вставь ![](url) первой строкой ПОСЛЕ H1. Нет картинки — осознанно оставь без неё (сайт сгенерирует фолбэк), но помни: статья без картинки в теле уязвима к затиранию обложки при будущих PUT.
Валидация. validate_article — доведи errors до пустых. Warnings взвесь: на молодом сайте (мало статей) warning про внутренние ссылки — норма.
Публикуй. publish_article (большой текст — через contentFile). Slug узнаешь только из ответа — ссылки НА новую статью ставь после этого шага: suggest_links по новому slug покажет доноров, правь их через update_article.
Индексация. IndexNow сервер пингует сам. Если у сайта задан yandexHost И доступен MCP yandex-marketing — предложи yd_webmaster_recrawl_submit (host_id = yandexHost из конфига, см. setup). Нет Яндекса — шаг пропусти.

Read the full file on GitHub · 56 lines

Files

What ships with it

3 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.

Changes

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 · 56 lines · 130 tokens per session scan A e21e7d23f9cd

Subscribe to this mod's changes

seo-content-factory is a skill published in the GitHub repository skiddgoddamn/seo-factory-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 130 tokens to every session and 1,090 once invoked, about $0.0006 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-31.

Marketing and SEO Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens