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 Hainrixz/claude-seo-ai --skill auditgit clone --depth 1 https://github.com/Hainrixz/claude-seo-aiWrote 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/hainrixz/claude-seo-ai/audit)<a href="https://agentmods.dev/skills/hainrixz/claude-seo-ai/audit"><img src="https://agentmods.dev/badge/skills/hainrixz/claude-seo-ai/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/hainrixz/claude-seo-ai/audit"><img src="https://agentmods.dev/badge/skills/hainrixz/claude-seo-ai/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.00127 | $0.00913 |
| Opus 5 | $0.00063 | $0.00456 |
| Sonnet 5 | $0.00025 | $0.00183 |
| Haiku 4.5 | $0.00013 | $0.00091 |
Grade A, and why
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 4d 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 — 26 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/claude-seo-ai:audit
A full, read-only SEO + AI-search audit. Never writes to the user's project; artifacts go to ${CLAUDE_PLUGIN_DATA}/runs (or --out).
$ARGUMENTS = <url|path> [flags]. The target is a URL (https://…) or a local web project / built HTML. If no target is given, ask for one. Flags are forwarded verbatim to the orchestrator, which passes them to audit.mjs: --pages N (pages to sample, default 12) · --max N (URLs to consider, default 40) · --render static|auto|js (default static — a headless run never launches a browser unless asked) · --ua default|googlebot|bingbot|gptbot|oai-searchbot|claude-searchbot (or a literal UA string) · --vertical <ids> (comma list of saas,blog-publisher,local-business,ecommerce,docs,generic; omit it to let the run infer one) · --environment production|preview|staging|local · --feed <path> (a product feed for the ACP lint) · --out <dir> (runs root; defaults to ${CLAUDE_PLUGIN_DATA}/runs).
What to do
- Invoke the seo-orchestrator skill with the target and all flags. It runs
audit.mjsonce — acquisition (crawl/snapshot → PageSnapshot v2), platform profile, vertical guess and the whole deterministic checks registry in a single call — refines the vertical with seo-vertical-detect (references/routing.md), dispatches the read-only specialist subagents in parallel with a dispatch envelope, then merges everything back withreport.mjs --mergeand scores. - Present, from
report.json:- The two scores — Search SEO and AI Visibility — each with a band (A–F) and a one-line interpretation. Never blended.
- A per-category breakdown for each score; coverage mode (full vs deterministic-only), the data tier reached, and the
needs_api/manual_reviewcounts (score confidence). - The sampling table: pages crawled by role, templates discovered vs sampled, and every skip with its reason.
- The platform profile (platform/framework/plugins, environment — e.g. "noindex expected on preview").
- A prioritized action list sorted by impact ÷ effort: status, evidence, recommendation, fixability (auto/proposed/advisory),
expected_impact(axis + confidence + magnitude). - The absolute report path (
<run_dir>/report.md).
- End by offering: "Run
/claude-seo-ai:fix <target>to apply the safe, deterministic fixes — you'll confirm each change" and "/claude-seo-ai:compare --baseline latest --against <target>after you deploy".
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.
- 4d ago Changed 08b0730b5916
- 6d ago Changed · +3 lines · +5 tokens per session f7f28e21c5dd
- 12d ago First seen · 23 lines · 122 tokens per session scan A e4bd4eca4c3f
audit is a skill published in the GitHub repository Hainrixz/claude-seo-ai (59 stars, last pushed 5d ago), licensed MIT. It adds 127 tokens to every session and 913 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-30.
Other skills, from other repositories
linkedin-post
Draft a daily LinkedIn post for S M Moshiur Rahman about business development, grounded in a real problem he hit that day and real numbers from OmniRank. Use when he says "linkedin post", "today's post", "draft a post", or describes friction he wants written up.
audit
Use when asked to audit a site's SEO, check AEO or answer-engine readiness, diagnose why a page is not ranking or not being cited by AI, verify structured data, or run pre-deploy discoverability checks on built HTML.
geo-artifacts
Use when asked to generate or fix llms.txt, llms-full.txt or facts.json, make a site citable or ingestible by ChatGPT, Claude, Perplexity or Gemini, or publish machine-readable ground truth for AI crawlers.
web-optimization
Audit or generate web content optimized for traditional search (SEO), AI generative answer engines like ChatGPT/Perplexity/Google AI Overviews (GEO), and answer engines / featured snippets / voice (AEO). Use when the user asks to improve a page's ranking or AI-citability, run an SEO/GEO/AEO audit of a URL or file, add…
fire-your-seo-agency
A procedure for improving how a website appears in search engines and how AI answer systems find and cite it. It covers search, answer-engine, generative-AI, and Naver visibility.
ansvisor-aeo-coach-standalone
Standalone (no-MCP) version of the Ansvisor AEO Coach. Use this only when the user's Claude client cannot connect to the Ansvisor MCP server (e.g. claude.ai web without a Connector configured). Fetches live data from the Ansvisor REST API directly with the user's API key via code execution. For clients that support…