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 sergekostenchuk/ui-ux-agent-skill-system --skill site-growth-orchestratorgit clone --depth 1 https://github.com/sergekostenchuk/ui-ux-agent-skill-systemWrote 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/ui-ux-agent-skill-system/site-growth-orchestrator)<a href="https://agentmods.dev/skills/sergekostenchuk/ui-ux-agent-skill-system/site-growth-orchestrator"><img src="https://agentmods.dev/badge/skills/sergekostenchuk/ui-ux-agent-skill-system/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/ui-ux-agent-skill-system/site-growth-orchestrator"><img src="https://agentmods.dev/badge/skills/sergekostenchuk/ui-ux-agent-skill-system/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.00983 |
| Opus 5 | $0.00055 | $0.00491 |
| Sonnet 5 | $0.00022 | $0.00197 |
| Haiku 4.5 | $0.00011 | $0.00098 |
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 12d 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.
This is a copy
100% identical to site-growth-orchestrator — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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
4 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.
- 12d ago First seen · 100 lines · 110 tokens per session scan A 51fad6b8cc5c
site-growth-orchestrator is a skill published in the GitHub repository sergekostenchuk/ui-ux-agent-skill-system (23 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 110 tokens to every session and 983 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to site-growth-orchestrator, differing in 2 lines, and is treated as a copy.
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…
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.
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…
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…