Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/seranking/seo-skillsnpx agentmods add skills/seranking/seo-skills/seo-googleWrote 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/seranking/seo-skills/seo-google)<a href="https://agentmods.dev/skills/seranking/seo-skills/seo-google"><img src="https://agentmods.dev/badge/skills/seranking/seo-skills/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/seranking/seo-skills/seo-google"><img src="https://agentmods.dev/badge/skills/seranking/seo-skills/seo-google.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00222 | $0.04889 |
| Opus 5 | $0.00111 | $0.02445 |
| Sonnet 5 | $0.00044 | $0.00978 |
| Haiku 4.5 | $0.00022 | $0.00489 |
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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- seo-google — 100% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 399 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Example output: examples/seo-google-quickstart-20260514/README.md
Google SEO APIs
Direct access to Google's own SEO data. Bridges the gap between crawl-based analysis (the rest of the catalogue) and Google's real-time field data: actual Chrome user metrics, real indexation status, search performance, and organic traffic.
All APIs are free. Setup requires a Google Cloud project with API key and/or service account — run the setup command for step-by-step instructions, or read references/auth-setup.md directly.
Adapted from
AgriciDaniel/claude-seo'sseo-googleskill (MIT). Scripts, references, and command surface mirror the upstream implementation. Config path namespaced to~/.config/seo-skills/for clean coexistence with the original.
Prerequisites
- Required: Python 3.10+ and the Google API client libraries. Install via
bash extensions/google/install.sh. - Required: at minimum a Google API key (Tier 0). For full coverage, also a Google Cloud service account (Tier 1+) and optionally a GA4 property ID (Tier 2) and Google Ads developer token (Tier 3).
- Config file:
~/.config/seo-skills/google-api.json.
Before executing any command, check credentials:
python scripts/google_auth.py --check --json
Config file shape (~/.config/seo-skills/google-api.json):
{
"service_account_path": "/path/to/service_account.json",
"api_key": "AIzaSy...",
"default_property": "sc-domain:example.com",
"ga4_property_id": "properties/123456789"
}
If missing, read references/auth-setup.md and walk the user through setup.
Credential Tiers
| Tier | Detection | Available Commands |
|---|---|---|
| 0 (API Key) | api_key present |
pagespeed, crux, crux-history, youtube, nlp, entity, safety |
| 1 (OAuth/SA) | + OAuth token or service account | Tier 0 + gsc, inspect, sitemaps, index |
| 2 (Full) | + ga4_property_id configured |
Tier 1 + ga4, ga4-pages, ga4-referrals, ga4-channel-mix, ga4-properties |
| 3 (Ads) | + ads_developer_token + ads_customer_id |
Tier 2 + keywords, volume |
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/templates/cwv-audit-report.md 1.5 KB
- assets/templates/gsc-performance-report.md 1.2 KB
- assets/templates/indexation-status-report.md 1.1 KB
- references/auth-setup.md 5.8 KB
- references/cross-skill-integration.md 9.9 KB
- references/ga4-data-api.md 5.2 KB
- references/indexing-api.md 3.1 KB
- references/keyword-planner-api.md 2.3 KB
- references/nlp-api.md 2.0 KB
- references/pagespeed-crux-api.md 6.2 KB
- references/rate-limits-quotas.md 3.3 KB
- references/search-console-api.md 4.6 KB
- references/supplementary-apis.md 2.7 KB
- references/youtube-api.md 1.5 KB
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.
- 10d ago First seen · 399 lines · 222 tokens per session scan A b094e9ae1314
seo-google is a skill published in the GitHub repository seranking/seo-skills (139 stars, last pushed 2mo ago), licensed MIT. It adds 222 tokens to every session and 4,889 once invoked, about $0.0011 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-30.
Other skills, from other repositories
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
analytics-strategy
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement.…
content-strategy
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align…
incident-response
Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers…
agb-begriff-vorformuliert-305
Für AGB Begriff Vorformuliert 305: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: agb-begriff-vorformuliert-305.
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.