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/skills/zacharticulatev/designer-pro-and-seo/seo-google)<a href="https://agentmods.dev/skills/zacharticulatev/designer-pro-and-seo/seo-google"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/seo-google/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-google"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/seo-google.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.00128 | $0.01146 |
| Opus 5 | $0.00064 | $0.00573 |
| Sonnet 5 | $0.00026 | $0.00229 |
| Haiku 4.5 | $0.00013 | $0.00115 |
Grade A, and why
seo-google 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
seo-google
Family: seo Status: Stable
Purpose
The "real field data" layer for the SEO family — Google's own measurements of how
real users experience a site, versus the synthetic/lab heuristics in seo-technical.
It is tool-aware: when a Google Search Console MCP (or Google APIs) is connected
it returns true field data; when nothing is connected it still delivers a real
on-page technical + GEO read and names precisely what to connect to unlock field
data. It never just fails.
What field data adds when connected:
- Search Console — impressions, clicks, CTR, average position; URL Inspection; sitemap status
- PageSpeed Insights / CrUX — real-user Core Web Vitals (LCP, INP, CLS), with CrUX's multi-week history
- GA4 — organic traffic, engagement, conversions
Triggers
- "search console" / "GSC"
- "pagespeed" / "PSI"
- "crux" / "field data" / "real CWV data"
- "indexing api" / "URL inspection"
- "ga4 organic" / "ga4 seo"
- "LCP" / "INP" / "CLS" / "FCP" / "TTFB"
- "impressions" / "clicks" / "CTR" / "position"
Inputs
- Domain or page URL
- Which signal is wanted (search analytics | URL inspection | field CWV | organic traffic)
- Optional: date range / comparison window
Steps
- Detect available tooling. Run
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/workflow/capability_probe.py"(env keys) and check whether a Search Console / Google MCP is exposed this session. - Field-data path (Tier 1, if connected). Call the connected GSC/Google MCP or Google APIs for the requested signal; normalize into a compact table; for CrUX, overlay the available history.
- Built-in path (Tier 2, always available). Fetch the page with WebFetch and
run
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/seo/tech_audit.py"(on-page technical: title/meta, canonical, robots, viewport, structured-data presence, security headers, INP<200ms guidance) andpython3 "${CLAUDE_PLUGIN_ROOT}/scripts/seo/geo_check.py"(AI-citability + llms.txt). This is real, useful output on its own — it just isn't field data. - Report which tier ran and, if field data wasn't available, the one-line setup to unlock it (connect a Search Console MCP, or set Google API OAuth).
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 · 93 lines · 128 tokens per session scan A 1b466584e40b
seo-google is a skill published in the GitHub repository ZachArticulateV/designer-pro-and-seo (8 stars, last pushed 2mo ago), licensed MIT. It adds 128 tokens to every session and 1,146 once invoked, about $0.0006 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.
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…
figma-variable-audit
Audit Figma variable collections against token architecture best practices. Trigger when someone says: audit my Figma variables, check my Figma tokens, are my variables structured correctly, Figma variable health, review my variable collections, variable naming check, or anything about auditing the quality or…
governance-encoder
Convert governance policies into machine-executable JSON constraint files that AI agents and CI pipelines validate against automatically. This produces rule engine files in .ai/governance/, NOT narrative decision records or documentation. Trigger when someone says: encode governance rules, governance as code, automate…
system-benchmark
Benchmark a design system against industry standards and comparable public systems, producing a qualitative comparison across dimensions with specific, named reference points. Goes beyond an internal health assessment to answer 'how does our system compare to what good looks like out there?' Trigger when someone says…