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 kabde/seo-skills --skill seo-auditgit clone --depth 1 https://github.com/kabde/seo-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/kabde/seo-skills/seo-audit)<a href="https://agentmods.dev/skills/kabde/seo-skills/seo-audit"><img src="https://agentmods.dev/badge/skills/kabde/seo-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/kabde/seo-skills/seo-audit"><img src="https://agentmods.dev/badge/skills/kabde/seo-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.00046 | $0.00826 |
| Opus 5 | $0.00023 | $0.00413 |
| Sonnet 5 | $0.00009 | $0.00165 |
| Haiku 4.5 | $0.00005 | $0.00083 |
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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full Website SEO Audit
Process
- Fetch homepage: use
scripts/fetch_page.pyto retrieve HTML - Detect business type: analyze homepage signals (WordPress, publisher, SaaS, etc.)
- Crawl site: follow internal links up to 500 pages, respect robots.txt
- Delegate to subagents (parallel when possible, sequential fallback):
seo-technical-- robots.txt, sitemaps, canonicals, Core Web Vitals, security headersseo-content-- E-E-A-T, readability, thin content, AI citation readinessseo-schema-- detection, validation, generation recommendationsseo-performance-- LCP, INP, CLS measurementsseo-visual-- screenshots, mobile testing, above-fold analysisseo-geo-- AI crawler access, llms.txt, citability, brand mention signalsseo-wordpress-- WordPress-specific audit via REST API (spawn when WordPress detected: wp-content, wp-json signals)seo-cluster-- Semantic clustering analysis (spawn when blog/content strategy signals detected)
- Score -- aggregate into SEO Health Score (0-100)
- Report -- generate prioritized action plan
Crawl Configuration
Max pages: 500
Respect robots.txt: Yes
Follow redirects: Yes (max 3 hops)
Timeout per page: 30 seconds
Concurrent requests: 5
Delay between requests: 1 second
Output Files
FULL-AUDIT-REPORT.md: Comprehensive findingsACTION-PLAN.md: Prioritized recommendations (Critical > High > Medium > Low)
Scoring Weights
| Category | Weight |
|---|---|
| Technical SEO | 22% |
| Content Quality | 23% |
| On-Page SEO | 20% |
| Schema / Structured Data | 10% |
| Performance (CWV) | 10% |
| AI Search Readiness | 10% |
| Images | 5% |
Report Structure
Executive Summary
- Overall SEO Health Score (0-100)
- Business type detected
- Top 5 critical issues
- Top 5 quick wins
Sections
- Technical SEO (crawlability, indexability, security, CWV)
- Content Quality (E-E-A-T, thin content, readability)
- On-Page SEO (titles, meta, headings, internal linking)
- Schema & Structured Data
- Performance (LCP, INP, CLS)
- Images (alt text, sizes, formats)
- AI Search Readiness (citability, GEO signals)
- WordPress Health (if WordPress detected)
What ships with it
1 file 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 · 93 lines · 46 tokens per session scan A 5ff4868335b9
seo-audit is a skill published in the GitHub repository kabde/seo-skills (11 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 826 once invoked, about $0.0002 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
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…