agentmods.dev

seo-growth-loop

seo-growth-loop is a skill for Claude Code from skiddgoddamn/seo-factory-mcp. It costs 157 tokens per session (1,000 once invoked), scanned A, original, MIT.

A Russian-language SEO workflow for growing a blog through the seo-factory MCP service. SEO means improving a site's visibility in search results; the workflow audits search data, orphan articles, and content, then creates a prioritised plan and carries it out.

In plain words
What is it for?
Use it to find queries ranking around the second search-results page, identify articles without incoming links, audit content for items such as FAQs and internal links, and plan or execute improvements.
Why use it?
It turns recurring blog SEO checks into a user-triggered workflow without needing a background server. For Russian sites, it can use Yandex Webmaster data when the required connection and site setting are available.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the seo-factory plugin — 2 skills, 1 MCP server shipped together

not rated 0repo 1mo ago A scan 157 tokens original MIT

Good fit Use it to find queries ranking around the second search-results page, identify articles without incoming links, audit content for items such as FAQs and internal links, and plan or execute improvements.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/skiddgoddamn/seo-factory-mcp/seo-growth-loop
View source ↗ skiddgoddamn/seo-factory-mcp
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-growth-loop
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.

agentmods badge for seo-growth-loop

README.md
[![agentmods](https://agentmods.dev/badge/skills/skiddgoddamn/seo-factory-mcp/seo-growth-loop/github.svg)](https://agentmods.dev/skills/skiddgoddamn/seo-factory-mcp/seo-growth-loop)
Your own site
<a href="https://agentmods.dev/skills/skiddgoddamn/seo-factory-mcp/seo-growth-loop"><img src="https://agentmods.dev/badge/skills/skiddgoddamn/seo-factory-mcp/seo-growth-loop/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.

agentmods 80×15 button for seo-growth-loop

Your own site · 80×15
<a href="https://agentmods.dev/skills/skiddgoddamn/seo-factory-mcp/seo-growth-loop"><img src="https://agentmods.dev/badge/skills/skiddgoddamn/seo-factory-mcp/seo-growth-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 157 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,000 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00157 $0.01000
Opus 5 $0.00078 $0.00500
Sonnet 5 $0.00031 $0.00200
Haiku 4.5 $0.00016 $0.00100

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

Security

Grade A, and why

seo-growth-loop 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-growth-loop/SKILL.md · 54 lines

How it starts

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

SEO цикл роста

Замена «SEO-агентов на кроне» из гайдов: тот же цикл, но запускается по запросу пользователя, без сервера. Для RU-сайтов первоисточник данных — Яндекс.Вебмастер (НЕ Google Search Console: на RU-трафике GSC часто пуст).

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

  1. Данные поиска (если доступны). Условие: у сайта задан yandexHost (см. setup) И подключён MCP yandex-marketing. Тогда:

    • yd_webmaster_search_queries_popular с host_id = yandexHost, order_by: "TOTAL_SHOWS", query_indicator: ["TOTAL_SHOWS","TOTAL_CLICKS","AVG_SHOW_POSITION"], период — последние 2-4 недели;
    • отфильтруй сам: AVG_SHOW_POSITION 8–30 и заметные показы — это «вторая страница», самый дешёвый трафик (уже ранжируется, надо дожать);
    • запиши в JSON-файл массив [{query, shows, position}] (query_text→query, TOTAL_SHOWS→shows, AVG_SHOW_POSITION→position) и вызови match_queries с queriesFile.
    • ⚠️ Вебмастер-API без ретраев: словил 429 — подожди, не долби.

    Нет Яндекса (нет yandexHost или MCP) — пропусти шаг, отметь в отчёте «данные поиска недоступны», работай локальным циклом (шаги 2-3).

  2. Структурный аудит. audit_orphans (сироты + доноры) и audit_content (нет FAQ / короткие / без обложки в теле / мало ссылок). На большом сайте — оба с saveToFile.

  3. Сводный план по приоритету:

    1. boost-запросы из match_queries — дожать существующие статьи (обновить контент под запрос, добавить FAQ-пару с формулировкой запроса, внутренние ссылки);
    2. сироты — добавить входящие ссылки из статей-доноров;
    3. new-запросы — новые статьи (скилл seo-content-factory);
    4. FAQ-бэкфилл и обложки из audit_content. Покажи план пользователю с оценкой объёма, дождись подтверждения.

  4. Исполнение. Правки существующих — update_article (⚠️ тул сам ловит затирание обложки; slug стабилен, URL не ломаются). Новые статьи — через скилл seo-content-factory.

  5. Индексация и контроль. Если Яндекс доступен: yd_webmaster_recrawl_submit на затронутые URL (квоту смотри yd_webmaster_recrawl_quota); yd_webmaster_insearch_samples — проверить, что дожатые страницы в поиске. IndexNow за create/update сервер шлёт сам. Через 1-2 недели повтори цикл и сравни позиции — это и есть петля роста.

Read the full file on GitHub · 54 lines

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.

  1. 11d ago First seen · 54 lines · 157 tokens per session scan A 113c582b33be

Subscribe to this mod's changes

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

Other skills, from other repositories

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

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

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens