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 Bomx/seo-keyword-research --skill google-search-consolegit clone --depth 1 https://github.com/Bomx/seo-keyword-researchWrote 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/bomx/seo-keyword-research/google-search-console)<a href="https://agentmods.dev/skills/bomx/seo-keyword-research/google-search-console"><img src="https://agentmods.dev/badge/skills/bomx/seo-keyword-research/google-search-console/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/bomx/seo-keyword-research/google-search-console"><img src="https://agentmods.dev/badge/skills/bomx/seo-keyword-research/google-search-console.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.00054 | $0.03175 |
| Opus 5 | $0.00027 | $0.01588 |
| Sonnet 5 | $0.00011 | $0.00635 |
| Haiku 4.5 | $0.00005 | $0.00317 |
Grade A, and why
google-search-console scanned grade A with 2 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
import urllib.parse Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
os.system(f"{sys.executable} -m pip install requests") How it starts
The opening of the file, as written. The whole thing — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FIRST TIME READING THIS SKILL? STOP AND READ THIS SECTION TO THE USER.
Before running any commands, explain the following to the user:
What Google Search Console gives you: Google Search Console (GSC) contains your actual search performance data — every keyword Google shows your site for, how many people clicked, your average position, and which pages rank. This data is free and comes directly from Google. Combining it with keyword research lets you find quick wins (keywords you already rank for but could optimize) and validate which keywords actually drive traffic.
What you need: A Google Cloud project with OAuth credentials. The project does NOT need to be published or verified by Google — it stays in "Testing" mode. You add your own email as a test user and that's it. No approval process, no review, no fees.
How long it takes: About 5 minutes to set up the Google Cloud project. After that, you run a one-time auth script and you're done.
Setup: Create a Google Cloud Project
Follow these steps to create OAuth credentials. Claude Code cannot do this for you — it requires clicking through the Google Cloud Console UI.
Step 1: Create the project
- Go to console.cloud.google.com
- Click the project dropdown at the top and select "New Project"
- Name it anything (e.g. "SEO Keyword Research")
- Click "Create"
Step 2: Enable the Search Console API
- In your new project, go to APIs & Services > Library
- Search for "Google Search Console API"
- Click it and press Enable
Step 3: Configure the OAuth consent screen
- Go to APIs & Services > OAuth consent screen
- Select External user type, click Create
- Fill in the required fields:
- App name: anything (e.g. "SEO Research")
- User support email: your email
- Developer contact email: your email
- Click Save and Continue
- On the Scopes page, click Add or Remove Scopes
- Search for
webmasters.readonlyand check it - Click Update, then Save and Continue
- On the Test Users page, click Add Users
- Add your own Google email address (the one that has Search Console access)
- Click Save and Continue, then Back to Dashboard
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 · 344 lines · 54 tokens per session scan A 1cb835f381c3
google-search-console is a skill published in the GitHub repository Bomx/seo-keyword-research (21 stars, last pushed 5mo ago), licensed MIT. It adds 54 tokens to every session and 3,175 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…