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.
git 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/agents/zacharticulatev/designer-pro-and-seo/seo-page)<a href="https://agentmods.dev/agents/zacharticulatev/designer-pro-and-seo/seo-page"><img src="https://agentmods.dev/badge/agents/zacharticulatev/designer-pro-and-seo/seo-page/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-page"><img src="https://agentmods.dev/badge/agents/zacharticulatev/designer-pro-and-seo/seo-page.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.01312 |
| Opus 5 | $0.00038 | $0.00656 |
| Sonnet 5 | $0.00015 | $0.00262 |
| Haiku 4.5 | $0.00008 | $0.00131 |
Grade A, and why
seo-page 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 11d 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-page (dispatched-leaf agent)
Wraps: skills/seo-page/SKILL.md — same method, no forked logic.
Method
The single-page analyzer: fetch one URL (WebFetch) — or read a local HTML file — and
run the same on-page, meta, content, schema, image, performance, and internal-link
checks a full audit runs, scoped to one page, then group findings by priority. Deep
schema goes to seo-schema, deep E-E-A-T to seo-content, and real field CWV to
seo-google (prose cross-references — not calls).
WebFetch <URL> # fetch the raw HTML inline; for a local build, Read the file directly
Check: one descriptive <title> (≤ ~60 chars), a ~150–160 char meta description,
exactly one <h1> with logical heading order, canonical, meta robots, and Open
Graph / Twitter tags; content depth and target-keyword presence without stuffing;
JSON-LD presence and type fit; image alt/format/dimensions/lazy-loading; observable
render-blocking and payload issues; and internal-link count plus anchor quality.
Group findings Critical / High / Medium / Low, each with a specific fix. Synthetic
fetch cannot measure field Core Web Vitals — never synthesize a field LCP/CLS/INP;
report observable issues, emit a needs_tier1 note, and route to seo-google when
the user has Google access.
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.
- 11d ago First seen · 98 lines · 76 tokens per session scan A 710d66c9ea3d
seo-page is an agent published in the GitHub repository ZachArticulateV/designer-pro-and-seo (8 stars, last pushed 2mo ago), licensed MIT. It adds 76 tokens to every session and 1,312 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
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-css
CSS design system specialist — generates BEM-named styles using custom properties, mobile-first responsive design, no build tools.
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.
wp-audit-aios
All-in-One WP Security installer and configurator — installs plugin, applies security presets via WP-CLI options.