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 oegeyilmaz9/seo-aeo-geo-ultimate/plugin install seo-aeo-geo-ultimateWrote 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/oegeyilmaz9/seo-aeo-geo-ultimate/seo-commerce)<a href="https://agentmods.dev/skills/oegeyilmaz9/seo-aeo-geo-ultimate/seo-commerce"><img src="https://agentmods.dev/badge/skills/oegeyilmaz9/seo-aeo-geo-ultimate/seo-commerce/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/oegeyilmaz9/seo-aeo-geo-ultimate/seo-commerce"><img src="https://agentmods.dev/badge/skills/oegeyilmaz9/seo-aeo-geo-ultimate/seo-commerce.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.00076 | $0.00731 |
| Opus 5 | $0.00038 | $0.00365 |
| Sonnet 5 | $0.00015 | $0.00146 |
| Haiku 4.5 | $0.00008 | $0.00073 |
Grade A, and why
seo-commerce 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 12d 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commerce SEO
Audit the complete product-discovery system: visible product/category pages, structured data, merchant feeds, change notification, policy fields, and documented AI commerce integrations. Keep every platform-specific control scoped to current primary documentation.
Read commerce-evidence-protocol.md before a formal audit.
Procedure
- Define markets, locales, storefront domains, catalog scope, product identifiers, feed destinations, currencies, inventory systems, and the decision owner.
- Capture representative visible product/category pages, raw/rendered markup, Product/MerchantListing data, canonical/index state, merchant feed rows, platform diagnostics, and update timestamps.
- Reconcile identifiers and buyer-visible facts across page, structured data, and feeds: name, brand, GTIN/MPN/SKU, variants, price/currency, availability, condition, shipping, returns, seller, reviews, and promotions.
- Inspect crawlable navigation, variants, facets, pagination, canonical handling, product retirement, out-of-stock behavior, image/video assets, and sitemap/feed discovery.
- Evaluate Merchant Center, Bing shopping, OpenAI product/merchant data, ACP/UCP, or other commerce capabilities only when the current platform documents the exact integration. Treat protocol discovery as optional capability, not ranking leverage.
- For frequently changing URLs, evaluate IndexNow or platform feed updates with exact changed-URL scope, key verification, rate handling, logs, owner, and rollback. Notification is not an indexing guarantee.
- Separate confirmed defects, platform-recommended opportunities, experiments, and unknowns. Route page markup to
seo-schema, crawl/index issues toseo-technical, query evidence toseo-research, agent task flows toseo-agentic, and measurement toseo-performanceorai-visibility-monitor. - Package production-relevant findings as SEO Findings
1.1.0inseo-findings.json, usingfeed,web_page,template,protocol_capability, or site targets andcommerce/freshnesscategories. Validate beforeseo-action-plan.
What ships with it
2 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.
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.
- 12d ago First seen · 34 lines · 76 tokens per session scan A 16e90f3ec3fa
seo-commerce is a skill published in the GitHub repository oegeyilmaz9/seo-aeo-geo-ultimate (2 stars, last pushed 22d ago), licensed Apache-2.0. It adds 76 tokens to every session and 731 once invoked, about $0.0004 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-31.
Other skills, from other repositories
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-aeo-coach
Acts as an Answer Engine Optimization (AEO) analyst for users running Ansvisor. Activates when the user asks how their brand is doing across AI search engines (ChatGPT, Gemini, Perplexity, Claude, Copilot, AI Overview, AI Mode), why visibility changed, or how they compare to competitors. Uses the Ansvisor MCP server…
seo-vertical-detect
Classify a website as ecommerce, local-business, blog-publisher, saas, docs, or generic (multiple may apply), and report detected locales, from the persisted PageSnapshot plus the platform detector's vertical hints. Used by seo-orchestrator to decide which conditional modules to run and how to reweight the scores.
seo-fix-apply
Writer protocol preloaded into the seo-fixer-writer agent — how confirmed SEO/AI-search fixes are applied (git pre-flight, backup, Edit/Write for local diffs, ticketed adapter CLIs for remote targets, re-verify, publish only on a second ticket, rollback) and the findings-array output contract. Used only by the fix…
audit
Audit a website or web codebase for SEO and AI-search (GEO/AEO) — produces two independent 0-100 scores (Search SEO + AI Visibility) plus a prioritized, evidence-backed report persisted on disk. Read-only; never writes to the project. Use when the user asks to audit, analyze, check, or score a site's SEO, structured…
orangeo-ai-visibility-skill
Audit brand AI visibility readiness and prepare OranGEO-style GEO, AEO, LLM SEO, and AI search optimization action plans. Use when asked for a Claude Code skill, Codex skill, GEO skill, generative engine optimization skill, answer engine optimization skill, AI visibility audit, AI search visibility checker, llms.txt…