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 agentmods add skills/citedy/adclaw/seo-googlenpx skills add citedy/adclaw --skill seo-googlegit clone --depth 1 https://github.com/citedy/adclawWrote 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/citedy/adclaw/seo-google)<a href="https://agentmods.dev/skills/citedy/adclaw/seo-google"><img src="https://agentmods.dev/badge/skills/citedy/adclaw/seo-google.svg" alt="Measured on agentmods" 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.00160 | $0.03263 |
| Opus 5 | $0.00080 | $0.01631 |
| Sonnet 5 | $0.00032 | $0.00653 |
| Haiku 4.5 | $0.00016 | $0.00326 |
Grade A, and why
seo-google scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> via `curl`/`httpx` with the reference docs in `seo-shared/references/google/`. This is a copy
86% identical to seo-google — 34 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google SEO APIs
Note: This skill references helper scripts (
scripts/google_auth.py, etc.) from the upstream claude-seo project. In AdClaw, use the Google APIs directly viacurl/httpxwith the reference docs inseo-shared/references/google/.
Direct access to Google's own SEO data. Bridges the gap between crawl-based analysis (existing claude-seo skills) 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 /seo google setup for step-by-step instructions.
Prerequisites
Before executing any command, check credentials:
python scripts/google_auth.py --check --json
Config file: ~/.config/claude-seo/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 seo-shared/references/google/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 |
| 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 |
| 3 (Ads) | + ads_developer_token + ads_customer_id |
Tier 2 + keywords, volume |
Always communicate the detected tier before running commands.
Quick Reference
| Command | What it does | Tier |
|---|---|---|
/seo google setup |
Check/configure API credentials | -- |
/seo google pagespeed <url> |
PSI Lighthouse + CrUX field data | 0 |
/seo google crux <url> |
CrUX field data only (p75 metrics) | 0 |
/seo google crux-history <url> |
25-week CWV trend analysis | 0 |
/seo google gsc <property> |
Search Console: clicks, impressions, CTR, position | 1 |
/seo google inspect <url> |
URL Inspection: index status, canonical, crawl info | 1 |
/seo google inspect-batch <file> |
Batch URL Inspection from file | 1 |
/seo google sitemaps <property> |
GSC sitemap status | 1 |
/seo google index <url> |
Submit URL to Indexing API | 1 |
/seo google index-batch <file> |
Batch submit up to 200 URLs | 1 |
/seo google ga4 [property-id] |
GA4 organic traffic report | 2 |
/seo google ga4-pages [property-id] |
Top organic landing pages | 2 |
/seo google youtube <query> |
YouTube video search (views, likes, duration) | 0 |
/seo google youtube-video <id> |
YouTube video details + top comments | 0 |
/seo google nlp <url-or-text> |
NLP entity extraction + sentiment + classification | 0 |
/seo google entities <url-or-text> |
Entity analysis only (for E-E-A-T) | 0 |
/seo google keywords <seed> |
Keyword ideas from Google Ads Keyword Planner | 3 |
/seo google volume <keywords> |
Search volume lookup from Keyword Planner | 3 |
/seo google entity <query> |
Knowledge Graph entity check | 0 |
/seo google safety <url> |
Web Risk URL safety check | 0 |
/seo google quotas |
Show rate limits for all APIs | -- |
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.
- 2d ago First seen · 350 lines · 160 tokens per session scan A 81e9febb7900
seo-google is a skill published in the GitHub repository citedy/adclaw (35 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 160 tokens to every session and 3,263 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 86% identical to seo-google, differing in 34 lines, and is treated as a copy.
Other skills, from other repositories
skill-creator
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
update-setup
One-time setup wizard for the nanobot upgrade skill. Triggers: setup update, configure update, 设置更新, 初始化更新.
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
image-generation
Generate images and iteratively edit saved image artifacts.
cron
Schedule reminders and recurring tasks.
summarize
Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).