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 softspark/ai-toolkit --skill seo-validategit clone --depth 1 https://github.com/softspark/ai-toolkitWrote 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/softspark/ai-toolkit/seo-validate)<a href="https://agentmods.dev/skills/softspark/ai-toolkit/seo-validate"><img src="https://agentmods.dev/badge/skills/softspark/ai-toolkit/seo-validate.svg" alt="Measured on agentmods" 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.00059 | $0.04021 |
| Opus 5 | $0.00030 | $0.02011 |
| Sonnet 5 | $0.00012 | $0.00804 |
| Haiku 4.5 | $0.00006 | $0.00402 |
Grade A, and why
seo-validate 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 3d 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/seo-validate — SEO Validation Scanner
$ARGUMENTS
Scan a codebase for SEO issues using pattern-matching heuristics. Detects W3C/HTML violations, meta tag gaps, structured data problems, hreflang errors, Core Web Vitals risks (LCP/INP/CLS), resource-hint misuse, above-the-fold anti-patterns, GEO gaps (chunk architecture, hedging language, decision frameworks, semantic triples, freshness), topical authority gaps (pillar/cluster structure, orphan pages, cannibalization), SPA/CSR/SSG crawlability problems, technical SEO misconfigurations, and accessibility-for-SEO issues. Read-only — never modifies files.
Standards basis: W3C HTML5 Recommendation, W3C WCAG 2.2, Schema.org vocabulary, IETF RFC 5646 (BCP 47 language tags) for hreflang, web.dev Core Web Vitals thresholds (LCP <2.5s, INP <200ms, CLS <0.1), Google Search Central crawlability guidelines, and emerging GEO (Generative Engine Optimization) practices.
Usage
/seo-validate # Scan full project, auto-detect framework
/seo-validate src/ # Scan specific path
/seo-validate --scope rendering # Only SPA/CSR/SSG crawlability checks
/seo-validate --scope performance # Only Core Web Vitals static signals
/seo-validate --scope geo # Only GEO (Generative Engine Optimization)
/seo-validate --scope topical # Only topical authority and cluster architecture
/seo-validate --severity high # Filter to HIGH findings only
/seo-validate --framework next # Force framework (skip auto-detection)
/seo-validate --rendering csr # Force rendering-mode interpretation
/seo-validate --output json # Structured JSON output for CI integration
Scopes:
full(default) — all 10 categoriestechnical— HTML semantics, hreflang, CWV, rendering, technical SEO (categories 1, 4, 5, 7, 8)content— meta/OG, structured data, GEO, a11y-for-SEO (categories 2, 3, 6, 9)performance— only CWV static signals (category 5)geo— only GEO / citability checks (category 6)rendering— only category 7 (SPA/CSR/SSG crawlability) — useful for migration auditstopical— only topical authority and cluster architecture (category 10)
What ships with it
10 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.
- reference/ai-pipeline.md 11 KB
- reference/content-citability.md 14 KB
- reference/core-web-vitals.md 13 KB
- reference/geo-aeo-patterns.md 8.7 KB
- reference/geo-guidelines.md 12 KB
- reference/scanner-categories.md 23 KB
- reference/schema-types.md 11 KB
- reference/spa-ssg-patterns.md 12 KB
- reference/w3c-guidelines.md 9.4 KB
- scripts/seo-scanner.py 19 KB runs code
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.
- 3d ago First seen · 246 lines · 59 tokens per session scan A 7701f632f942
seo-validate is a skill published in the GitHub repository softspark/ai-toolkit (170 stars, last pushed 2d ago), licensed Apache-2.0. It adds 59 tokens to every session and 4,021 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
cline-fix-volatile-msg
Ladder-aware Cline Anthropic caching — verify the rolling read/write ladder on the wire, then add the tools breakpoint and tune TTL. Updated for the 2026-08 AI-SDK monorepo.
aider-1h-ttl
Aider uses 5min TTL by default and works around long pauses with keepalive pings. Wire up the 1h TTL beta instead.
continue-enable-defaults
Continue's prompt caching is opt-in via config and off by default. Flip the default to systemAndTools.
continue-gemini-explicit
Continue's Gemini provider doesn't use the cachedContents API at all. Add explicit caching for sessions over the minimum token threshold.
opencode-bedrock-doc-blocks
OpenCode places cachePoint on Bedrock messages containing DocumentBlocks, which produces a "nothing available to cache" error.
roo-fix-volatile-msg
Ladder-aware Roo Code Anthropic caching — verify the rolling read/write ladder on the wire, then close the real gaps (Vertex 4-block budget, MiniMax path).