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/VKirill/claude-lane-stacknpx agentmods add skills/vkirill/claude-lane-stack/google-search-consoleWrote 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/vkirill/claude-lane-stack/google-search-console)<a href="https://agentmods.dev/skills/vkirill/claude-lane-stack/google-search-console"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/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/vkirill/claude-lane-stack/google-search-console"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/google-search-console.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 21 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Tool Misuse · line 118 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00172 | $0.04982 |
| Opus 5 | $0.00086 | $0.02491 |
| Sonnet 5 | $0.00034 | $0.00996 |
| Haiku 4.5 | $0.00017 | $0.00498 |
Grade A, and why
google-search-console 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 4d 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Version Requirements (May 2026)
Primary pins:
- Search Console API:
v1(Webmasters v3 endpoints stable; URL Inspection onsearchconsole.googleapis.com/v1) - Indexing API:
v3(JobPosting + BroadcastEvent only) - Python:
3.14.x - Node.js:
24.x (Active LTS)
Source of truth: STACK_VERSIONS.md — verified 2026-08-24
Usage
Loaded automatically when the description matches the active task. Read only the section you need, then follow the link to the relevant reference file for full detail.
Use this skill when
- Pull search analytics data (queries, pages, countries, devices, searchAppearance) for content planning, position audits, or client reports.
- Programmatically check URL index status via
urlInspection.index.inspect(verdict, coverageState, lastCrawlTime, googleCanonical vs userCanonical, mobileUsability, AMP, richResults). - Submit / delete / list
sitemap.xmlfor an added property (/webmasters/v3/sites/{siteUrl}/sitemaps). - Manage sites list (URL-prefix property vs Domain property
sc-domain:example.com) and check permission level. - Notify Google about a new or deleted page via Indexing API — only for JobPosting or BroadcastEvent. Regular pages will not work and abuse risks revoke.
- Build a Python (
google-api-python-client+google-auth) or Node.js (googleapis) client with service account and automatic 25k-cap pagination. - Schedule a daily ETL of search analytics into PostgreSQL —
(query, page, country, device, date) → clicks/impressions/ctr/position. - Audit indexation on large sites via URL Inspection while respecting the 2000/day/property quota.
Do not use this skill when
- You need Yandex Webmaster — different provider, different property/sitemap model; → cascade
yandex-webmaster. - You need GA4 web analytics (sessions, users, events) — GSC only returns Google search data; → cascade
google-analytics. - You need Bing Webmaster Tools — separate Microsoft API.
- You need generic Google OAuth2 / service account patterns; → cascade
google-cloud-auth. - You need true SERP positions with real locale/device — GSC returns averaged impressions/position for queries already discovered; real SERP snapshot → cascade
xmlstock. - You expect a "list all my indexed URLs" endpoint — Google does not provide one; sample via Sitemaps + URL Inspection.
- You want to force-index regular pages with Indexing API — abuse-banned, alternative is sitemap + internal links + UI "Request Indexing".
What ships with it
9 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.
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.
- 4d ago First seen · 267 lines · 172 tokens per session scan A 6089a5122c4c
google-search-console is a skill published in the GitHub repository VKirill/claude-lane-stack (115 stars, last pushed today), licensed MIT. It adds 172 tokens to every session and 4,982 once invoked, about $0.0009 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-09-05.
Other skills, from other repositories
gingiris-seo-geo-agent
SEO/GEO Agent Operations SOP v2 — Rebuilt from real-world operations (analook.com 0→launch, GSC incident, DataForSEO monitoring, gingiris.tools post-migration recovery). What's new in v2: • Step-by-step onboarding (Q1→Q6), multiple choice wherever possible — no big forms • Mandatory daily SEO log — first item is…
google-workspace
Google Docs, Sheets, and Drive operations via REST API.
google-search-console-cli
Google Search Console data analysis and site management via google-search-console-cli. Use when the user wants to check search performance, analyze queries, inspect URL index status, manage sitemaps, or view site properties. Triggers: "Search Console", "search performance", "search queries", "GSC", "index status"…
afc:learner
Review and promote learned patterns to project rules.
afc:release-notes
Generate release notes from git history.
afc:clean
Pipeline artifact cleanup and codebase hygiene.