Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sergekostenchuk/seo-llm-skill-clusternpx agentmods add skills/sergekostenchuk/seo-llm-skill-cluster/site-growth-orchestratorWrote 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/sergekostenchuk/seo-llm-skill-cluster/site-growth-orchestrator)<a href="https://agentmods.dev/skills/sergekostenchuk/seo-llm-skill-cluster/site-growth-orchestrator"><img src="https://agentmods.dev/badge/skills/sergekostenchuk/seo-llm-skill-cluster/site-growth-orchestrator/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/sergekostenchuk/seo-llm-skill-cluster/site-growth-orchestrator"><img src="https://agentmods.dev/badge/skills/sergekostenchuk/seo-llm-skill-cluster/site-growth-orchestrator.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.00110 | $0.00973 |
| Opus 5 | $0.00055 | $0.00487 |
| Sonnet 5 | $0.00022 | $0.00195 |
| Haiku 4.5 | $0.00011 | $0.00097 |
Grade A, and why
site-growth-orchestrator 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 13d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- site-growth-orchestrator — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Site Growth Orchestrator
Use this skill as the routing and governance layer for site-growth work. It coordinates specialist skills, task plans, artifacts, validation, and release gates. It does not replace the specialists.
Core Rule
Own sequence, evidence, handoff quality, and stop conditions. Delegate domain judgments.
- SEO/schema architecture goes to
technical-seo-schema-engineeror existingseo-llm-site-architect. - Semantic core goes to
semantic-core-architect. - URL architecture goes to
information-architecture-seo. - Internal linking goes to
internal-link-graph-architect. - LLM-readable site layers go to
llm-friendly-site-architect. - Validation goes to
seo-regression-validatorandcluster-consistency-linter. - UX journeys go to
ui-ux-llm-product-architect. - Security boundaries go to
web-security-architect. - External authority placement is approval-first and post-MVP.
Read references/workflow.md before handling broad multi-step requests.
Modes
triage: classify a user request, identify owners, blockers, required evidence, and next task.plan: create or update a TASK-PLAN v2 with dependencies, alarms, test gates, and artifacts.execute: route work to the next specialist sequence and keep the plan state current.review: compare outputs against the goal, artifacts, task plan, and validation evidence.release: decide whether a staged skill/site-growth workflow can be packaged, deployed, or needs rollback.
Workflow
- Restate the concrete objective and current artifact state.
- Identify the primary owner skill and the supporting skills.
- Check active alarms, unknown credentials, freshness-sensitive facts, and external-action boundaries.
- Choose the next smallest unblocked task.
- Prepare a handoff packet using assets/handoff-packet.template.md when another specialist needs context.
- Require evidence before marking work complete: file paths, commands, reports, browser checks, live URLs, or source links.
- Update the task plan and validation artifacts before committing.
- Stop or defer work that needs secrets, account access, external posting, legal approval, or live production changes not approved by the user.
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.
- 13d ago First seen · 100 lines · 110 tokens per session scan A ec4b3b25c885
site-growth-orchestrator is a skill published in the GitHub repository sergekostenchuk/seo-llm-skill-cluster (39 stars, last pushed 3mo ago), licensed MIT. It adds 110 tokens to every session and 973 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-30.
Other skills, from other repositories
technocore-chat
Coordinate with other AI agents over plain HTTP GETs — shared rooms, durable notes, long-polling. No POST, no sockets, no client libraries, no account; a fetch tool is enough, and an MCP server fronts the same surface. Use when you need to leave a message for another agent, wait for one, or persist state across your…
dialectical-paper-writing
Analyze, design, write, revise, translate, and review empirical or technical research papers through an evidence-bounded dialectical workflow. Use when Codex must develop a research question, integrate reference papers with a user's ideas, build phenomenon-mechanism-conditions reasoning, design methods or experiments…
wiki-ingest
Compile a raw source (document, URL content, meeting notes, research output) into a wikikit agent wiki — merge-don't-overwrite, log contradictions, maintain cross-references, then lint. Use whenever the user says "add this to the wiki", "ingest this", or drops new source material for a wiki maintained with…
agent-pitbook
Search and contribute to Agent Pitbook, a structured debugging pit knowledge base for coding agents. Use when Codex is diagnosing recurring local-development failures, sandbox issues, dependency installation errors, Docker or port problems, MCP/tool quirks, browser automation failures, or when a verified debugging…
duckduckgo-search
Free keyless web, news, and image search via ddgs.
mcporter
List, auth, and call MCP servers/tools from the terminal.