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 AgentlyLabs/founder-skills --skill seo-auditgit clone --depth 1 https://github.com/AgentlyLabs/founder-skillsWrote 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/agentlylabs/founder-skills/seo-audit)<a href="https://agentmods.dev/skills/agentlylabs/founder-skills/seo-audit"><img src="https://agentmods.dev/badge/skills/agentlylabs/founder-skills/seo-audit/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/agentlylabs/founder-skills/seo-audit"><img src="https://agentmods.dev/badge/skills/agentlylabs/founder-skills/seo-audit.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.00231 | $0.02532 |
| Opus 5 | $0.00115 | $0.01266 |
| Sonnet 5 | $0.00046 | $0.00506 |
| Haiku 4.5 | $0.00023 | $0.00253 |
Grade A, and why
seo-audit 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.
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Audit via Google Search Console
Why this skill exists
Most SEO audits fail in one of two ways. They either dump every crawler warning into a 200-row spreadsheet with no sense of what actually costs money, or they assert causes ("your rankings dropped because of the algorithm update") that the available data cannot support.
This skill exists to avoid both. The core discipline is: every finding is tied to measured GSC data, states the mechanism behind it, and carries an impact estimate whose arithmetic is shown so the user can disagree with it. A finding you cannot quantify or explain is an observation, not a recommendation, and belongs in an appendix.
The second discipline is honesty about what Search Console can and cannot tell you. A
large fraction of published "GSC audit" advice quietly assumes data the API does not
expose. Getting this wrong produces confident, wrong conclusions — see
references/gsc-api-surface.md for exactly where the boundaries are.
Step 0 — Find the Search Console connection
There is no single canonical GSC MCP server, so do not assume tool names. Discover them:
- Search for the tools with
ToolSearchusing queries likesearch console,+searchconsole,google seo analytics. Load whatever matches. - If nothing loads, check the MCP registry (
search_mcp_registrywith keywords like["google search console", "seo"]) and surface connect options withsuggest_connectors. - Confirm which properties the connection can actually see before planning anything —
the equivalent of
sites.list. Property type matters: a domain property (sc-domain:example.com) aggregates all subdomains and protocols, a URL-prefix property (https://example.com/) does not. Auditing a URL-prefix property and reporting it as whole-site truth is a common and invisible error.
If no GSC connection exists, say so plainly and offer the fallback: a best-practice-only audit from crawling the live site (Step 4), clearly labeled as having no performance data behind it. Do not silently degrade into a generic checklist — the user asked for an audit grounded in their data, and they should know if they aren't getting one.
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.
- 11d ago First seen · 190 lines · 231 tokens per session scan A 3cfc6b0b5555
seo-audit is a skill published in the GitHub repository AgentlyLabs/founder-skills (2 stars, last pushed 14d ago), licensed MIT. It adds 231 tokens to every session and 2,532 once invoked, about $0.0012 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.
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…
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…
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…
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…