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-geo)<a href="https://agentmods.dev/agents/zacharticulatev/designer-pro-and-seo/seo-geo"><img src="https://agentmods.dev/badge/agents/zacharticulatev/designer-pro-and-seo/seo-geo/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-geo"><img src="https://agentmods.dev/badge/agents/zacharticulatev/designer-pro-and-seo/seo-geo.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.00108 | $0.01368 |
| Opus 5 | $0.00054 | $0.00684 |
| Sonnet 5 | $0.00022 | $0.00274 |
| Haiku 4.5 | $0.00011 | $0.00137 |
Grade A, and why
seo-geo 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
seo-geo (dispatched-leaf agent)
Wraps: skills/seo-geo/SKILL.md — same method, no forked logic.
Method
Optimize for being cited inline by the AI answer rather than ranking #1: run the
bundled GEO checker with the weighted scorecard, then rewrite the weak passages it
lists so each leads with one specific, sourced, standalone claim. Structured-data
work defers to seo-schema and the content-quality lens is shared with
seo-content (prose cross-references — not calls).
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/seo/geo_check.py" --content page.html --robots robots.txt --scorecard --human # add --url https://site.com for llms.txt + live robots
It scores each passage's citability (sourced + self-contained + answer-first →
0-100), counts structured-data blocks, reads the robots AI-crawler policy, and rolls
those signals into a weighted 0-100 GEO score re-normalized over whatever signals
are present (so a content-only offline run still scores). Read the crawler-policy
verdict (citable-training-blocked is best practice; retrieval-blocked is the
anti-pattern), flag missing llms.txt, and render platform-specific action items.
Never fabricate an LLM-mention count — emit it as a labeled needs_tier1 proxy.
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 · 97 lines · 108 tokens per session scan A baf6b5a8857f
seo-geo is an agent published in the GitHub repository ZachArticulateV/designer-pro-and-seo (8 stars, last pushed 2mo ago), licensed MIT. It adds 108 tokens to every session and 1,368 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 agents, from other repositories
geo-routing-engineer
Geospatial and routing specialist for Product-Builder products with maps, scheduling-by-location, or vehicle routing (route-optimization in logistics, dispatch in home services, field-booking). Owns the routing contract — geocoding, the VRP/routing model (constraints, objective), maps/distance-matrix provider…
ai-agent
AI feature implementation specialist. Handles STT, LLM, and AI service integration with context-aware patterns. Auto-discovers project conventions before implementing. Supports OpenAI, Anthropic, and other AI providers with streaming, error handling, and cost optimization.
unfolding-po
PO (Product Owner) role in the Unfolding Specs process. Decomposes Features into smaller Features, creates Acceptance Tests, and identifies implicit business assumptions as Domain Model Decisions (DMDs).
mlops
ML infrastructure specialist — training pipelines, model serving, GPU optimization, distributed training.
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.