A toolset for retrieving and examining Google Search Console data, which reports how a site appears in Google Search.

Use it to pull search reports, inspect URLs, investigate indexing problems, and manage sitemaps after publishing pages.

It gives developers data about searches, pages, clicks, indexing, and visibility instead of relying on assumptions about how Google sees the site.

gsc — Skill for Claude Code by lisbeth718/pseo-skills

Install

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.

Any agent

npx skills add lisbeth718/pseo-skills --skill gsc

Clone the repo

git clone --depth 1 https://github.com/lisbeth718/pseo-skills

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/gsc/github.svg)](https://agentmods.dev/skills/lisbeth718/pseo-skills/gsc)

Your own site

<a href="https://agentmods.dev/skills/lisbeth718/pseo-skills/gsc"><img src="https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/gsc/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/lisbeth718/pseo-skills/gsc"><img src="https://agentmods.dev/badge/skills/lisbeth718/pseo-skills/gsc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,497 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00055	$0.02497
Opus 5.5	$0.00022	$0.00999
Sonnet 5.5	$0.00011	$0.00499
Haiku 4.5	$0.00006	$0.00250

Measured 6d ago against content hash b826358bcc39, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gsc 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 6d ago.

The scan reads SKILL.md. This mod also ships 5 executable files (scripts/auth.ts, scripts/inspect.ts, scripts/lib/auth.ts, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/gsc/SKILL.md · 168 lines

How it starts

The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Google Search Console

Pull, analyze, and act on Google Search Console data for any site. In the pSEO pipeline this is the post-launch monitoring step: run it after pseo-quality-guard once pages are live and the sitemap is submitted.

Facts below are from docs/research-2026-10.md (2026-10-12).

Prerequisites

Scripts live in this skill's scripts/ folder (<skill-dir>/scripts/, for example .claude/skills/gsc/scripts/). Install once:

cd <skill-dir>/scripts && npm install

Credentials (override paths with env vars GSC_CLIENT and GSC_TOKENS):

OAuth client: ~/.config/gsc-oauth-client.json
OAuth tokens: ~/.config/gsc-oauth-tokens.json

If tokens don't exist, follow the Setup section. Never commit these files.

Determine the site property

sc-domain:example.com (domain property, covers all subdomains)
https://example.com/ (URL prefix property)

Try the domain property first. On a permission error, try the URL prefix version.

Actions

pull (default)

Default 28 days, configurable with --days.

npx tsx <skill-dir>/scripts/pull.ts --site sc-domain:example.com --days 28
# explicit range (overrides --days), full page coverage, custom output file
npx tsx <skill-dir>/scripts/pull.ts --site sc-domain:example.com --start 2026-07-01 --end 2026-09-28 --pages 25000 --out data/gsc-current.json
# full query+page dataset for cannibalization work
npx tsx <skill-dir>/scripts/pull.ts --site sc-domain:example.com --dims query,page --out data/gsc-qp.json

Run from the project root. Output goes to ./data/gsc-queries.json in the current working directory unless --out <path> is given. The script fetches (paginating with startRow):

Top 500 queries with clicks, impressions, CTR, position (--queries N)
Top 200 pages with the same metrics (--pages N; use --pages 25000 for full page coverage)
Per-page query breakdown for the top 30 pages (--top-pages N)
With --dims query,page: the full query+page dataset (25,000 rows per request, paginated) in a queryPages array. This can be large and counts against load quotas.

Read the full file on GitHub · 168 lines

Files

What ships with it

7 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.

Changes

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.

6d ago First seen · 168 lines · 55 tokens per session scan A b826358bcc39

Subscribe to this mod's changes

gsc is a skill published in the GitHub repository lisbeth718/pseo-skills (54 stars, last pushed 6d ago), licensed MIT. It adds 55 tokens to every session and 2,497 once invoked, about $0.0002 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-10-12.

Analytics and metrics Marketing and SEO

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

microsoft/vscode · 72 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.