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 powehi-eu/google-suite-seo-mcp --skill google-seo-auditgit clone --depth 1 https://github.com/powehi-eu/google-suite-seo-mcpWrote 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/powehi-eu/google-suite-seo-mcp/google-seo-audit)<a href="https://agentmods.dev/skills/powehi-eu/google-suite-seo-mcp/google-seo-audit"><img src="https://agentmods.dev/badge/skills/powehi-eu/google-suite-seo-mcp/google-seo-audit/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/powehi-eu/google-suite-seo-mcp/google-seo-audit"><img src="https://agentmods.dev/badge/skills/powehi-eu/google-suite-seo-mcp/google-seo-audit.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.00025 | $0.00242 |
| Opus 5 | $0.00013 | $0.00121 |
| Sonnet 5 | $0.00005 | $0.00048 |
| Haiku 4.5 | $0.00003 | $0.00024 |
Grade A, and why
google-seo-audit 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.
What it actually says
Google SEO Audit
Use this skill when the user asks for Google-backed SEO evidence, especially GSC queries, GA4 performance context, or CrUX field data.
Evidence Order
- Confirm credentials with
scripts/check-auth.ps1. - Use GSC MCP for indexed/search performance evidence.
- Use GA4 MCP for acquisition and engagement context.
- Use
scripts/crux-query.mjsfor origin-level CrUX field data. - Keep source/build/live/GSC/GA4/CrUX evidence separate in the final report.
Default Site
For world-models.io, default to:
- origin:
https://world-models.io - GSC property:
sc-domain:world-models.iowhen available, otherwise the URL-prefix property - GA4 property: ask the user only if it cannot be discovered from GA4 MCP
Safety
Never print private keys, refresh tokens, client secrets, or full credential JSON contents. Report only whether required files and keys are present.
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 · 29 lines · 25 tokens per session scan A fa6e63ae4182
google-seo-audit is a skill published in the GitHub repository powehi-eu/google-suite-seo-mcp (5 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 242 once invoked, about $0.0001 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
filter-structures
The correct shape for dimensionfilter in getga4data. Wrong structure returns an "Invalid dimensionfilter" error. Use these templates.
traffic-diagnosis
Systematically diagnose why traffic changed — spike, drop, or shift in mix. Follow these steps in order. Each step narrows the hypothesis.
ai-referral-analysis
Measure traffic arriving from AI tools — ChatGPT, Claude, Perplexity, Gemini, Copilot, and others — and understand how it behaves compared to other channels.
attribution-scope
GA4 has three distinct attribution scopes. Using the wrong scope gives misleading results. Choose based on the question you are answering.
bot-traffic-detection
Identify and exclude bot, scraper, and spam sessions from GA4 data.
content-performance
Identify top-performing pages, find underperforming content, and understand engagement patterns across your site.