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 gabrielmoreira/agent-skills-mirror --skill seo-growthgit clone --depth 1 https://github.com/gabrielmoreira/agent-skills-mirrorWrote 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/gabrielmoreira/agent-skills-mirror/seo-growth)<a href="https://agentmods.dev/skills/gabrielmoreira/agent-skills-mirror/seo-growth"><img src="https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/seo-growth/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/gabrielmoreira/agent-skills-mirror/seo-growth"><img src="https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/seo-growth.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00159 | $0.01802 |
| Opus 5 | $0.00079 | $0.00901 |
| Sonnet 5 | $0.00032 | $0.00360 |
| Haiku 4.5 | $0.00016 | $0.00180 |
Grade A, and why
seo-growth 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 9d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/seo-growth — first-party SEO growth method
Core principle: the right move depends on whether you have data yet, and most bad SEO advice is given to the wrong one of those two situations. A site with no rankings and a site with a breadwinner page need opposite behavior. Advice that ignores which you are in is how efforts stall despite consistent output.
Distilled from two content properties run in production and the Search Console reads that
produced each rule. This is a first-party method: narrower than a general playbook, and
more trustworthy for it. Every rule traces to the failure or result behind it in
references/why-these-rules.md. Absolute traffic figures are withheld; the ratios and
thresholds are as observed.
The two playbooks
| You are here if… | Playbook | Read |
|---|---|---|
| No rankings, no authority, <100 clicks/mo, possibly no content | A — Cold start | references/cold-start.md |
| GSC has real rows: something ranks, something earns clicks | B — With data | references/with-data.md |
Diagnose per cluster, not per site. A mature site opening a new territory is in Playbook A for that territory and Playbook B everywhere else — and that combination is the strongest position in the method.
Playbook A in one line: you cannot win an established term from zero authority, so hunt an emerging one, ship ONE page, and let day-7 / day-21 decide whether it was real.
Playbook B in one line: your own GSC already knows which page shapes win for you — find the breadwinner, extract the shape, diagnose whether it is position-limited or snippet-limited, compound it, and protect it while you do.
Read alongside either playbook
references/emerging-terms.md— the hunt. The wedge in both playbooks, and the only thing that works in Playbook A. Where to look, in what order, and the seven gates a candidate must pass.references/measurement.md— which metric scores which situation, the four query families that never click, and the GSC traps that produce confident wrong conclusions.references/why-these-rules.md— the failure or result behind each rule.references/operationalize.md— turning either playbook into scheduled loops.
What ships with it
7 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.
- 9d ago First seen · 131 lines · 159 tokens per session scan A 3cefafbb1562
seo-growth is a skill published in the GitHub repository gabrielmoreira/agent-skills-mirror (17 stars, last pushed yesterday), licensed MIT. It adds 159 tokens to every session and 1,802 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-09-03.
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…