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 Shiven0504/claude-skills-collection --skill seo-auditgit clone --depth 1 https://github.com/Shiven0504/claude-skills-collectionWrote 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/shiven0504/claude-skills-collection/seo-audit)<a href="https://agentmods.dev/skills/shiven0504/claude-skills-collection/seo-audit"><img src="https://agentmods.dev/badge/skills/shiven0504/claude-skills-collection/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/shiven0504/claude-skills-collection/seo-audit"><img src="https://agentmods.dev/badge/skills/shiven0504/claude-skills-collection/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.00121 | $0.02010 |
| Opus 5 | $0.00060 | $0.01005 |
| Sonnet 5 | $0.00024 | $0.00402 |
| Haiku 4.5 | $0.00012 | $0.00201 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
On-Page SEO Audit
Analyze source code files for on-page SEO issues and produce a clear, actionable markdown report. The goal is to catch real problems that hurt search rankings — not to nitpick or generate noise.
How to run an audit
-
Identify the files to audit. If the user points to specific files, use those. If they say "audit my site" or similar, look for page-level files — things like
index.html, Next.js pages (app/**/page.tsx,pages/**/*.tsx), or layout files. Use Glob to find them. -
Read each file and check against the checklist below.
-
Produce the report in the format described at the bottom.
What to check
Work through each section for every page file. Not every check applies to every file — use judgment. A shared <Header> component won't have a <title> tag, and that's fine.
Title tag
The <title> element (or metadata.title in Next.js) is the single most important on-page SEO signal.
Check for:
- Missing title entirely
- Title that's too short (under 20 characters) or too long (over 60 characters) — search engines truncate long titles
- Generic/meaningless titles like "Home", "Page", "Untitled", or the framework default
- Duplicate titles across pages (if auditing multiple pages)
Why it matters: The title tag is displayed as the clickable headline in search results. A clear, descriptive title with relevant keywords directly affects click-through rate and ranking.
Meta description
The <meta name="description"> tag (or metadata.description in Next.js).
Check for:
- Missing entirely — search engines will auto-generate one, but it's usually worse
- Too short (under 50 characters) or too long (over 160 characters)
- Doesn't summarize the page content or include relevant keywords
- Duplicate descriptions across pages
Why it matters: While not a direct ranking factor, the meta description appears as the snippet in search results and heavily influences click-through rate.
Heading structure
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 · 184 lines · 121 tokens per session scan A d18916cea78d
seo-audit is a skill published in the GitHub repository Shiven0504/claude-skills-collection (6 stars, last pushed 5mo ago), licensed MIT. It adds 121 tokens to every session and 2,010 once invoked, about $0.0006 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…