agentmods.dev

seo-score

seo-score is a skill for Claude Code from Hainrixz/claude-seo-ai. It costs 66 tokens per session (759 once invoked), scanned A, original, MIT.

A scoring method that turns website audit findings into separate 0–100 scores for search-engine optimisation and visibility in AI-generated answers. It applies category weights, finding severity, status, and score caps.

In plain words
What is it for?
Use it to calculate the two scores, assign A–F bands, apply severe-failure limits, and produce a short interpretation of the results.
Why use it?
It gives consistent results without mixing traditional search performance with AI visibility, while handling optional audit areas fairly.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the claude-seo-ai plugin — 34 skills, 5 agents, 1 hook shipped together

not rated 59repo +9 changed 4d ago A scan 66 tokens original MIT

Good fit Use it to calculate the two scores, assign A–F bands, apply severe-failure limits, and produce a short interpretation of the results.

Compare 6 skills from other repositories ↓
View source ↗ Hainrixz/claude-seo-ai tododeia.com
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add Hainrixz/claude-seo-ai
Claude Code
/plugin install claude-seo-ai

Made for: Claude Code.

Or install claude-seo-ai, the plugin that ships this one along with the rest of its 34 skills, 5 agents, 1 hook.

Wrote 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.

agentmods badge for seo-score

README.md
[![agentmods](https://agentmods.dev/badge/skills/hainrixz/claude-seo-ai/seo-score/github.svg)](https://agentmods.dev/skills/hainrixz/claude-seo-ai/seo-score)
Your own site
<a href="https://agentmods.dev/skills/hainrixz/claude-seo-ai/seo-score"><img src="https://agentmods.dev/badge/skills/hainrixz/claude-seo-ai/seo-score/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.

agentmods 80×15 button for seo-score

Your own site · 80×15
<a href="https://agentmods.dev/skills/hainrixz/claude-seo-ai/seo-score"><img src="https://agentmods.dev/badge/skills/hainrixz/claude-seo-ai/seo-score.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 759 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00066 $0.00759
Opus 5 $0.00033 $0.00380
Sonnet 5 $0.00013 $0.00152
Haiku 4.5 $0.00007 $0.00076

Measured 4d ago against content hash 31e89cb00f40, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

seo-score 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.

skills/seo-score/SKILL.md · 30 lines

How it starts

The opening of the file, as written. The whole thing — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.

seo-score

Turns findings (conforming to schema/finding.schema.json) into the two scores. Full model in references/scoring-model.md — follow it exactly.

Steps

  1. Group findings by the category each module maps to, per score. A finding contributes only to the score(s) in expected_impact.axis (search, ai, or both).
  2. Category value = 100 × Σ(status_factor × severity for scored findings) / Σ(severity), where status_factor: pass 1.0, warn 0.5, fail 0.0. Exclude needs_api and not_applicable from both sums.
  3. Active weights: drop conditional categories (e-commerce/local/international) whose modules produced no findings; re-normalize remaining weights to sum to their active total.
  4. Score = Σ(category_value × weight) / Σ(active weight) for each of Search SEO and AI Visibility.
  5. Severity gating: if any finding has severity: 5 and status: fail, cap the affected score at 40 and set capped: true.
  6. Assign bands (A≥90, B≥80, C≥70, D≥60, F<60) and a one-line interpretation from the Search×AI quadrant. 6b. Coverage floor: report coverage (the % of the axis's always-on weight that carried a scored finding). Below 50% the axis comes back provisional: true with state: "partial" — quote the band and the coverage figure together, never the letter on its own.
  7. M21 (AI discovery & agent endpoints — llms.txt, agents.md, UCP, agentic sitemap) weight is 0 — report it, never let it move the AI score.

Determinism

Prefer node "${CLAUDE_PLUGIN_ROOT}/scripts/score.mjs" --run <run-dir> (it reads <run-dir>/findings.json) or --findings <path> for a bare findings file, adding --vertical a,b, --multilingual and --environment production|preview|staging|local when the file carries no run context, so the number is reproducible and CI-checkable. --run takes a path, never the word latest: the score command resolves latest[:host] from <root>/<host>/latest.json first and passes the directory. If Node is unavailable, compute by hand following the same formula and note the fallback. Either way the math must match references/scoring-model.md.

Read the full file on GitHub · 30 lines

Changes

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.

  1. 4d ago Changed · +1 lines 31e89cb00f40
  2. 6d ago Changed · +1 lines 4004999679a8
  3. 12d ago First seen · 28 lines · 66 tokens per session scan A 4a72d2959665

Subscribe to this mod's changes

seo-score is a skill published in the GitHub repository Hainrixz/claude-seo-ai (59 stars, last pushed 5d ago), licensed MIT. It adds 66 tokens to every session and 759 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-08-30.

Analytics and metricsClaude CodeMarketing and SEOaeoai-searchanswer-engine-optimizationclaude-pluginclaude-skills
Related

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.

bemoshiur/OmniRank · 63 tokens

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.

bemoshiur/OmniRank · 49 tokens

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.

bemoshiur/OmniRank · 54 tokens

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…

staksoft/geo-seo-aeo-skill · 105 tokens

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.

leopard627/fire-your-seo-agency · 162 tokens

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…

ansvisor/ansvisor · 124 tokens