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 LeahyCC/claude-skills --skill seogit clone --depth 1 https://github.com/LeahyCC/claude-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/leahycc/claude-skills/seo)<a href="https://agentmods.dev/skills/leahycc/claude-skills/seo"><img src="https://agentmods.dev/badge/skills/leahycc/claude-skills/seo/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/leahycc/claude-skills/seo"><img src="https://agentmods.dev/badge/skills/leahycc/claude-skills/seo.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.00073 | $0.01855 |
| Opus 5 | $0.00036 | $0.00928 |
| Sonnet 5 | $0.00015 | $0.00371 |
| Haiku 4.5 | $0.00007 | $0.00186 |
Grade A, and why
seo 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 10d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO — Search & AI Engine Optimization
Production-ready SEO patterns for Next.js applications. Covers traditional SEO (Google), GEO (AI search engines), and implementation with actual code — not just recommendations.
This skill generates code, not audits. Every pattern includes production-ready Next.js App Router examples you can use directly.
Architecture Overview
[Metadata]
├── Static metadata (layout.tsx / page.tsx exports)
├── Dynamic metadata (generateMetadata with data fetching)
├── File-based (favicon.ico, opengraph-image.tsx, robots.ts, sitemap.ts)
└── Title templates (%s | Site Name)
↓
[Structured Data]
├── JSON-LD via <script type="application/ld+json">
├── Schema.org types (Article, Product, Organization, BreadcrumbList)
└── Rich results eligibility (FAQ, HowTo, Review, Video)
↓
[Crawlability]
├── robots.ts (Google + AI crawler control)
├── sitemap.ts (dynamic, with images and i18n)
├── Canonical URLs (alternates.canonical)
└── Internal linking
↓
[Performance (Ranking Factor)]
├── LCP — next/image priority, Server Components
├── INP — useTransition, code splitting
└── CLS — next/font, image dimensions
↓
[AI Visibility (GEO)]
├── llms.txt generation
├── Content structure for citation
├── AI crawler user-agent management
└── Entity optimization
Quick Reference
| Need to... | See |
|---|---|
| Add metadata to pages and layouts | Metadata |
| Create sitemap.xml and robots.txt | Crawlability |
| Add JSON-LD structured data | Structured Data |
| Generate dynamic OG images | OG Images |
| Optimize for AI search (ChatGPT, Perplexity) | GEO |
| Fix Core Web Vitals for SEO ranking | Performance |
| Avoid common SEO mistakes | Anti-Myths |
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.
- 10d ago First seen · 145 lines · 73 tokens per session scan A 057e30295d8b
seo is a skill published in the GitHub repository LeahyCC/claude-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 1,855 once invoked, about $0.0004 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
Accessibility Audit Helper
Reviews UI code and components for WCAG 2.1 accessibility violations and provides specific fixes.
wes-bos-sick-picks
Research-first workflow for building frontend UI components (any framework), in the spirit of Wes Bos. Use when designing or implementing a UI component, layout, interaction, or CSS/HTML feature and you want a modern, accessible, best-practice solution rather than a first guess. Researches pitfalls and platform…
wcag-accessibility
Apply and audit WCAG 2.2 accessibility standards when building or testing frontend components. ALWAYS use this skill when: building any UI component, page, or layout (even if the user doesn't mention accessibility); running accessibility audits or tests; asked to "check a11y", "test accessibility", "audit WCAG…
accessibility
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
performance
Optimize web performance for faster loading and better user experience. Use when asked to "speed up my site", "optimize performance", "reduce load time", "fix slow loading", "improve page speed", or "performance audit".
core-web-vitals
Optimize Core Web Vitals (LCP, INP, CLS) for better page experience using field and lab evidence. Use when asked to "improve Core Web Vitals", "fix LCP", "reduce CLS", "optimize INP", "page experience optimization", or "fix layout shifts".