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 amirjahfar1/Google-Search-Console-GSC-MCP --skill new-vs-lost-queriesgit clone --depth 1 https://github.com/amirjahfar1/Google-Search-Console-GSC-MCPWrote 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/amirjahfar1/google-search-console-gsc-mcp/new-vs-lost-queries)<a href="https://agentmods.dev/skills/amirjahfar1/google-search-console-gsc-mcp/new-vs-lost-queries"><img src="https://agentmods.dev/badge/skills/amirjahfar1/google-search-console-gsc-mcp/new-vs-lost-queries/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/amirjahfar1/google-search-console-gsc-mcp/new-vs-lost-queries"><img src="https://agentmods.dev/badge/skills/amirjahfar1/google-search-console-gsc-mcp/new-vs-lost-queries.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.00044 | $0.00435 |
| Opus 5 | $0.00022 | $0.00217 |
| Sonnet 5 | $0.00009 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
new-vs-lost-queries 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 11d 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.
What it actually says
New vs Lost Queries
compare_search_periods shows change for queries present in both periods. This skill goes further: it finds queries that are brand-new (zero presence before) and queries that vanished entirely (zero presence now) — both stronger signals than a simple ranking decline.
Steps
- Call
list_propertiesto confirm the exactsite_url. - Define two adjacent, equal-length periods (default: last 28 days = Period 2, the 28 days before that = Period 1).
- Call
get_advanced_search_analyticsfor Period 1 withdimensions=query,row_limit=1000,sort_by=impressions. - Call
get_advanced_search_analyticsfor Period 2 with the same parameters. - Build two sets of query strings, one per period.
- New queries = present in Period 2 but not Period 1 — sort by Period 2 impressions descending, take top 20.
- Lost queries = present in Period 1 but not Period 2 — sort by Period 1 impressions descending, take top 20.
- Lost queries with meaningful impressions (>50 in Period 1) are a stronger warning sign than a ranking decline — the page may have been deindexed, the content removed/changed, or a competitor took the spot.
Output format
- New Queries table: Query | Impressions | Clicks | Position (Period 2)
- Lost Queries table: Query | Impressions | Clicks | Position (Period 1, now zero)
- Net visibility change summary (impressions gained vs impressions lost)
Related skills
For any high-impression lost query tied to a specific page, run indexing-audit on that page to check if it dropped out of the index entirely.
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.
- 11d ago First seen · 32 lines · 44 tokens per session scan A c9c7de803afe
new-vs-lost-queries is a skill published in the GitHub repository amirjahfar1/Google-Search-Console-GSC-MCP (0 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 435 once invoked, about $0.0002 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-01.
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…
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…
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…