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/bestlemoon/codex-seo/seo-googlenpx skills add BestLemoon/codex-seo --skill seo-googlegit clone --depth 1 https://github.com/BestLemoon/codex-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/bestlemoon/codex-seo/seo-google)<a href="https://agentmods.dev/skills/bestlemoon/codex-seo/seo-google"><img src="https://agentmods.dev/badge/skills/bestlemoon/codex-seo/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 | $0.00160 | $0.03140 |
| Opus 5 | $0.00080 | $0.01570 |
| Sonnet 5 | $0.00032 | $0.00628 |
| Haiku 4.5 | $0.00016 | $0.00314 |
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 5d 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.
This is a copy
100% identical to seo-google — 0 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 — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google SEO APIs
Direct access to Google's own SEO data. Bridges the gap between crawl-based analysis (existing codex-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/codex-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 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 |
| 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 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
- LICENSE.txt 142 B
- references/auth-setup.md 5.1 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.
- 5d ago First seen · 346 lines · 160 tokens per session scan A 52e3166a37e2
seo-google is a skill published in the GitHub repository BestLemoon/codex-seo (9 stars, last pushed 2mo ago), licensed MIT. It adds 160 tokens to every session and 3,140 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to seo-google, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…