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 ZachArticulateV/designer-pro-and-seo --skill seo-ecommercegit clone --depth 1 https://github.com/ZachArticulateV/designer-pro-and-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/zacharticulatev/designer-pro-and-seo/seo-ecommerce)<a href="https://agentmods.dev/skills/zacharticulatev/designer-pro-and-seo/seo-ecommerce"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/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/zacharticulatev/designer-pro-and-seo/seo-ecommerce"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/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.00107 | $0.00611 |
| Opus 5 | $0.00053 | $0.00305 |
| Sonnet 5 | $0.00021 | $0.00122 |
| Haiku 4.5 | $0.00011 | $0.00061 |
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 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
seo-ecommerce
Family: seo Status: Stable
Purpose
E-commerce-specific SEO. The free path fully covers on-page product SEO and Product schema; marketplace intelligence (Google Shopping, Amazon) is the optional DataForSEO-Merchant path.
Triggers
- "ecommerce seo" / "product seo" / "merchant seo"
- "product schema" / "product listings"
- "google shopping" / "shopping ads" / "amazon seo" / "marketplace seo"
Inputs
- Domain or product URL(s)
- Marketplace coverage (Google Shopping / Amazon / both / none)
- Competitor domains (optional)
Steps
- Audit product pages (free path): unique, benefit-led titles + descriptions;
one h1; descriptive URL; internal links to category/related; review content
present. Run
seo-pageper key product. - Validate Product schema via
seo-schema: requirename+image; for merchant eligibility includeofferswithprice+priceCurrency+availability, plusaggregateRating/reviewonly when real. - Image SEO via
seo-image-audit(product photos are conversion- and ranking-critical: alt, format, size, CLS). - Category/faceted strategy — canonical handling for filters/sort, thin-variant
consolidation (coordinate with
seo-programmatic). - Marketplace (optional). If DataForSEO is configured, pull Google Shopping presence and Amazon/keyword-gap data; otherwise state what it would add and check feed basics manually.
- Render per-product scores, schema validation, and a prioritized fix list.
Outputs
- Per-product on-page scores + prioritized fixes
- Product schema validation report
- Marketplace presence/gap report (when DataForSEO present) or a manual checklist
Dependencies
seo-schema(Product schema),seo-page(per-product),seo-image-audit(images)- Optional: DataForSEO Merchant (Google Shopping/Amazon),
seo-programmatic(facets)
Notes
Conditional in seo-audit — fires on e-commerce signals (cart, checkout, Product
schema). Never fabricate ratings/reviews in schema — it's a manual action risk.
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 · 61 lines · 107 tokens per session scan A 86bac3ea4631
seo-ecommerce is a skill published in the GitHub repository ZachArticulateV/designer-pro-and-seo (8 stars, last pushed 2mo ago), licensed MIT. It adds 107 tokens to every session and 611 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-31.
Other skills, from other repositories
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
tripadvisor-cli
Searches TripAdvisor hotels, restaurants, attractions, and destinations via the cli-web-tripadvisor command-line tool, with detail lookups by URL. Use when the user asks about hotels, restaurants, things to do, travel destinations, or TripAdvisor ratings and reviews. Prefer this CLI over fetching the TripAdvisor…
token-audit
Audit a design system's token definitions for naming violations, missing semantic tiers, and structural debt. This audits how tokens are defined and organised, NOT how they are consumed in code. Trigger when someone says: audit my tokens, token naming review, are my tokens consistent, token health check, review my…
stakeholder-brief
Write a one-page stakeholder brief translating design system health or status into business language. Trigger when someone says: stakeholder update, exec brief, leadership summary, status report for leadership, system status for non-designers, write a brief for the business, or anything about communicating design…
cicd-integration
Generate CI/CD pipeline configurations that automate design system quality checks — token validation, component linting, visual regression, accessibility scanning, and release gating. Produces ready-to-use pipeline files for GitHub Actions, GitLab CI, CircleCI, or Bitbucket Pipelines, configured to enforce the…
codebase-index
Generate a pre-computed component index from a design system codebase — YAML infrastructure files containing a component inventory, relationship graph, and summary statistics that AI agents and MCP servers consume. This produces machine-readable index files in .ai/index/, NOT a health report or quality assessment.…