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 joaoguirunas/team-os --skill seo-googlegit clone --depth 1 https://github.com/joaoguirunas/team-osWrote 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/joaoguirunas/team-os/seo-google)<a href="https://agentmods.dev/skills/joaoguirunas/team-os/seo-google"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/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/joaoguirunas/team-os/seo-google"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/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.00098 | $0.04207 |
| Opus 5.5 | $0.00039 | $0.01683 |
| Sonnet 5.5 | $0.00020 | $0.00841 |
| Haiku 4.5 | $0.00010 | $0.00421 |
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 20d 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 — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google SEO APIs
Quando usar esta vs. traffic-ga4-mcp: esta cobre as APIs Google de SEO (Search Console, PageSpeed, CrUX, Indexing, GA4 orgânico). Para relatórios GA4 de campanhas pagas, validação de UTMs e conversões de ads, use traffic-ga4-mcp.
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:
"${CLAUDE_PROJECT_DIR}/.claude/skills/seo/scripts/claude-seo" run google_auth.py --check --json
Config file: ~/.config/claude-seo/google-api.json
{
"service_account_path": "/path/to/service_account.json",
"api_key": "<GOOGLE_API_KEY>",
"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
15 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.4 KB
- assets/templates/indexation-status-report.md 1.1 KB
- LICENSE.txt 286 B
- references/auth-setup.md 5.2 KB
- references/dma-consent-mode-v2.md 2.6 KB
- references/ga4-data-api.md 5.2 KB
- references/indexing-api.md 3.2 KB
- references/keyword-planner-api.md 2.3 KB
- references/nlp-api.md 2.3 KB
- references/pagespeed-crux-api.md 6.8 KB
- references/rate-limits-quotas.md 3.3 KB
- references/search-console-api.md 5.3 KB
- references/supplementary-apis.md 2.7 KB
- references/youtube-api.md 1.6 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.
- 20d ago Changed · -2 lines · -18 tokens per session a58a0ba01496
- 25d ago First seen · 364 lines · 116 tokens per session scan A 234194620b29
seo-google is a skill published in the GitHub repository joaoguirunas/team-os (4 stars, last pushed 2d ago), licensed MIT. It adds 98 tokens to every session and 4,207 once invoked, about $0.0004 per session on Opus 5.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-09-21.
Other skills, from other repositories
jsonl-log-analyzer
Analyze large JSONL log files using schema-aware partitioned analysis. Discovers field schema, generates tailored jq extraction recipes, and orchestrates parallel chunk analysts with synthesis. Use when processing JSONL logs exceeding context limits, performing log analytics, or investigating incident logs.
orchestration-patterns
Apply proven orchestration patterns for agent teams including parallel specialists, pipelines, swarms, research+implementation, plan approval, and multi-file refactoring. Use when choosing a team structure, designing workflows, or implementing specific coordination patterns.
task-system
Manage shared task lists for agent teams including creating tasks, setting dependencies, claiming work, and tracking progress. Use when creating work items, building task pipelines, coordinating task ownership, or managing task dependencies.
spawn-backends
Configure how teammate agents run including in-process, tmux, and iTerm2 backends. Use when choosing a display mode, setting up split panes, troubleshooting backend issues, or configuring teammateMode.
error-handling
Debug and recover from agent team errors including common errors, hooks for quality gates, known limitations, and recovery strategies. Use when encountering team errors, enforcing quality gates with hooks, understanding limitations, or debugging agent issues.
messaging
Send messages between agents using SendMessage including direct messages, broadcasts, shutdown requests/responses, and plan approvals. Use when communicating between agents, understanding message formats, or handling structured protocol messages.