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 ZachArticulateV/designer-pro-and-seo/plugin install 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/agents/zacharticulatev/designer-pro-and-seo/seo-ecommerce)<a href="https://agentmods.dev/agents/zacharticulatev/designer-pro-and-seo/seo-ecommerce"><img src="https://agentmods.dev/badge/agents/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/agents/zacharticulatev/designer-pro-and-seo/seo-ecommerce"><img src="https://agentmods.dev/badge/agents/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.00089 | $0.01285 |
| Opus 5 | $0.00044 | $0.00642 |
| Sonnet 5 | $0.00018 | $0.00257 |
| Haiku 4.5 | $0.00009 | $0.00128 |
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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
seo-ecommerce (dispatched-leaf agent)
Wraps: skills/seo-ecommerce/SKILL.md — same method, no forked logic.
Method
E-commerce-specific SEO on a store: audit product and category on-page signals
(unique benefit-led titles/descriptions, one h1, descriptive URL, internal links,
real review content), validate Product schema for merchant eligibility, and check
image SEO and faceted/canonical strategy for filters and variants. Deep schema goes
to seo-schema, per-product depth to seo-page, image depth to seo-image-audit,
and facet consolidation to seo-programmatic (prose cross-references — not calls).
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/seo/schema_gen.py" --validate product.json # Product-schema eligibility
Require name + image; for merchant eligibility include offers with price +
priceCurrency + availability. Include aggregateRating/review only when
real — never fabricate ratings or reviews into schema (it is a manual-action
risk). Google Shopping presence, Amazon marketplace visibility, and competitor
pricing are the DataForSEO-Merchant path; when it is not connected, audit feed
basics and on-page signals manually, emit a needs_tier1 note, and never synthesize
a marketplace or pricing number.
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 · 98 lines · 89 tokens per session scan A 4926aa5a0dcb
seo-ecommerce is an agent published in the GitHub repository ZachArticulateV/designer-pro-and-seo (8 stars, last pushed 2mo ago), licensed MIT. It adds 89 tokens to every session and 1,285 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 agents, from other repositories
connector-builder
Source-connector specialist for dashboard / analytics Product-Builder products. The read-side twin of integrations-engineer — owns the connector contract for pulling data IN from sources (Stripe, Google Analytics, QuickBooks, Google/Meta Ads, Shopify, carrier APIs): OAuth source auth, incremental sync (cursors/CDC)…
design-token-extractor
Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…
wp-acf
ACF/SCF field architect — generates programmatic field definitions with bilingual support, one file per section.
wp-cf7
CF7 form specialist — generates contact forms, branded email templates, and creates forms via WP-CLI with bilingual support.
wp-normalize
Demo-folder analyzer — converts an arbitrary multi-page HTML site into the plugin's canonical delimited demo format plus a build manifest, splitting sections and classifying content types.
wp-audit-a11y
Accessibility auditor — WCAG 2.1 AA compliance, WordPress-specific checks, skip links, ARIA, keyboard navigation, color contrast.