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 textura-agency/next16-claude-starter --skill seo-auditgit clone --depth 1 https://github.com/textura-agency/next16-claude-starterWrote 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/textura-agency/next16-claude-starter/seo-audit)<a href="https://agentmods.dev/skills/textura-agency/next16-claude-starter/seo-audit"><img src="https://agentmods.dev/badge/skills/textura-agency/next16-claude-starter/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/textura-agency/next16-claude-starter/seo-audit"><img src="https://agentmods.dev/badge/skills/textura-agency/next16-claude-starter/seo-audit.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.00089 | $0.00987 |
| Opus 5 | $0.00044 | $0.00494 |
| Sonnet 5 | $0.00018 | $0.00197 |
| Haiku 4.5 | $0.00009 | $0.00099 |
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 13d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO audit
Audit the code, and the live URL when one exists. Rank findings by impact and fix them; do not hand back a lecture.
1. Indexability — nothing else matters if this is broken
src/app/robots.ts— allows crawlers, points at the sitemap, no accidentaldisallow: /.src/app/sitemap.ts— every public route is listed. This is the one that rots: adding a route without a sitemap entry is the most common miss in this starter. Cross-checkfind src/app -name 'page.tsx'against the sitemap array.- Canonical URL on each page; no duplicate content across trailing-slash or parameter variants.
NEXT_PUBLIC_SITE_URLset in the deployed environment, sometadataBaseresolves OG/canonical to absolute URLs. Unset means social scrapers seelocalhost.- No route accidentally opted out of static rendering. Any
headers()/cookies()read — includingisBot()— forces dynamic rendering and costs TTFB on every visit.
2. Metadata
Every route exports metadata via generateMetadata in
src/utils/seo/generate-page-metadata.ts (obsidian/frontend/seo-metadata.md).
- Unique, specific
titleper route — not the site name repeated. descriptionper route, written for a human, 140–160 chars.- OG image present and correctly sized (1200×630 is the target; the shipped
open-graph.pngis 900×600 — flag it). themeColorviagenerateViewport, not on the metadata object.langon<html>; favicons and manifest present.
3. Content structure
- Exactly one
<h1>, matching what the page is actually about. - Heading outline is a real hierarchy with no skipped levels.
<main>present; landmarks named; lists are lists.- Answer-shaped content: the page states its answer near the top rather than building to it — this serves both featured snippets and AI extraction.
- Internal links use
<Link>, have descriptive anchor text (never "click here"), and no important page is orphaned. - Every image has meaningful
alt.
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.
- 13d ago First seen · 84 lines · 89 tokens per session scan A 2e5621279b84
seo-audit is a skill published in the GitHub repository textura-agency/next16-claude-starter (117 stars, last pushed 4d ago), licensed Unlicense. It adds 89 tokens to every session and 987 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-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…
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…