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.
/plugin marketplace add Hainrixz/claude-seo-ai/plugin install 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/seo-ecommerce)<a href="https://agentmods.dev/skills/hainrixz/claude-seo-ai/seo-ecommerce"><img src="https://agentmods.dev/badge/skills/hainrixz/claude-seo-ai/seo-ecommerce/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/seo-ecommerce"><img src="https://agentmods.dev/badge/skills/hainrixz/claude-seo-ai/seo-ecommerce.svg" alt="Reviewed on agentmods" width="80" 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.00096 | $0.02844 |
| Opus 5 | $0.00048 | $0.01422 |
| Sonnet 5 | $0.00019 | $0.00569 |
| Haiku 4.5 | $0.00010 | $0.00284 |
Grade A, and why
seo-ecommerce 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
seo-ecommerce (M18)
Conditional commerce module: it runs only when commerce signals are detected, then audits (a) product structured data for Search and (b) whether an AI shopping agent can actually read and act on the store. Reference: references/schema-tier1.md (Product + Offer, Review/AggregateRating rows). Platform-specific ids — Shopify's Catalog and UCP defaults among them — live in references/platforms/shopify.md and are emitted by the platform-conditional checks, not from here.
Inputs
Work from the PageSnapshot named in your dispatch envelope: read parsed from <run_dir>/pages/<slug>.json (jsonld[], metas[], text_sample) and vertical from the envelope — the commerce gate is decided there; <run_dir>/site/discovery.json carries the probes for /.well-known/ucp and /api/ucp/mcp (status, content-type, body); <run_dir>/profile.json names the platform. Grep pages/<slug>.html for verbatim evidence; site artifacts live in <run_dir>/site/{robots.json,sitemaps.json,discovery.json}. Deterministic findings already emitted by audit.mjs are listed in <run_dir>/findings.deterministic.json — do not re-emit those ids; add model-judged findings only. If invoked directly with a URL/path and no snapshot exists, first run node "${CLAUDE_PLUGIN_ROOT}/scripts/snapshot.mjs" <target> --out "${CLAUDE_PLUGIN_DATA}/runs" and use the printed snapshot path.
Audits
Working from the PageSnapshot (parsed_rendered when render.used is not none, else parsed):
- Commerce gate: detect commerce signals (price/currency text, add-to-cart/buy controls,
Product/Offerschema,og:type=product). If none, every M18 finding isnot_applicable(severity 0) — do not force product schema onto non-commerce pages. - Product + Offer:
Producthasname,image;Offerhasprice,priceCurrency,availability(schema.org/InStocketc.). Perreferences/schema-tier1.md. - AggregateRating / Review: if ratings are visibly shown, expect
AggregateRating(ratingValue,reviewCount/bestRating) and/orReview(author). Never mark up ratings that are not visible on the page. - Page → schema → feed consistency: schema
price/priceCurrency/availabilitymust match the visible on-page values and the merchant feed. Mismatches risk disapproval and lost rich results. - Faceted navigation: filter/sort URLs (
?color=,?sort=) should canonicalize to the clean product/category URL or benoindex, to avoid index bloat and duplicate-content dilution. - Variants / ProductGroup: multi-variant products should use
ProductGroupwithhasVariantandvariesBy, not duplicate standaloneProductblocks per SKU.
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 · +29 lines · +12 tokens per session 4fa3389c9ec2
- 5d ago Changed · +3 lines 615771fd0461
- 12d ago First seen · 41 lines · 84 tokens per session scan A 01a50ffc06a7
seo-ecommerce is a skill published in the GitHub repository Hainrixz/claude-seo-ai (59 stars, last pushed 4d ago), licensed MIT. It adds 96 tokens to every session and 2,844 once invoked, about $0.0005 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…
pricing-and-packaging
Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction. Use this to set or change pricing, design or restructure tiers, choose a pricing metric, build an offer, design upgrade prompts and paywalls, or evaluate whether a pricing…
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.