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 agentmods add skills/bestlemoon/codex-seo/seo-auditnpx skills add BestLemoon/codex-seo --skill seo-auditgit clone --depth 1 https://github.com/BestLemoon/codex-seoWrote 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/bestlemoon/codex-seo/seo-audit)<a href="https://agentmods.dev/skills/bestlemoon/codex-seo/seo-audit"><img src="https://agentmods.dev/badge/skills/bestlemoon/codex-seo/seo-audit.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.00062 | $0.01340 |
| Opus 5 | $0.00031 | $0.00670 |
| Sonnet 5 | $0.00012 | $0.00268 |
| Haiku 4.5 | $0.00006 | $0.00134 |
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 6d 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.
This is a copy
100% identical to seo-audit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 134 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 per seo orchestrator
- Crawl site: follow internal links up to 500 pages, respect robots.txt
- Delegate to subagents (if available, otherwise run inline sequentially):
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-sitemap-- structure analysis, quality gates, missing pagesseo-performance-- LCP, INP, CLS measurementsseo-visual-- screenshots, mobile testing, above-fold analysisseo-geo-- AI crawler access, llms.txt, citability, brand mention signalsseo-local-- GBP signals, NAP consistency, reviews, local schema, industry-specific local factors (spawn when Local Service industry detected: brick-and-mortar, SAB, or hybrid business type)seo-maps-- Geo-grid rank tracking, GBP audit, review intelligence, competitor radius mapping (spawn when Local Service detected AND DataForSEO MCP available)seo-google-- CWV field data (CrUX), URL indexation (GSC), organic traffic (GA4) (spawn when Google API credentials detected viapython scripts/google_auth.py --check)seo-backlinks-- Backlink profile data: DA/PA, referring domains, anchor text, toxic links (spawn when Moz or Bing API credentials detected viapython scripts/backlinks_auth.py --check, or always include Common Crawl domain-level metrics)
- 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)screenshots/: Desktop + mobile captures (if Playwright available)- PDF Report (recommended): Generate a professional A4 PDF using
scripts/google_report.py --type full. This produces a white-cover enterprise report with TOC, executive summary, charts (Lighthouse gauges, query bars, index donut), metric cards, threshold tables, prioritized recommendations with effort estimates, and implementation roadmap. Always offer PDF generation after completing an audit.
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.
- 6d ago First seen · 134 lines · 62 tokens per session scan A 05479879a578
seo-audit is a skill published in the GitHub repository BestLemoon/codex-seo (9 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 1,340 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to seo-audit, differing in 0 lines, and is treated as a copy.
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…