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 shutovdef-dotcom/google-search-console-mcp --skill cannibalization-checkgit clone --depth 1 https://github.com/shutovdef-dotcom/google-search-console-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/shutovdef-dotcom/google-search-console-mcp/cannibalization-check)<a href="https://agentmods.dev/skills/shutovdef-dotcom/google-search-console-mcp/cannibalization-check"><img src="https://agentmods.dev/badge/skills/shutovdef-dotcom/google-search-console-mcp/cannibalization-check/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/shutovdef-dotcom/google-search-console-mcp/cannibalization-check"><img src="https://agentmods.dev/badge/skills/shutovdef-dotcom/google-search-console-mcp/cannibalization-check.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.00037 | $0.00404 |
| Opus 5 | $0.00018 | $0.00202 |
| Sonnet 5 | $0.00007 | $0.00081 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
cannibalization-check 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 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.
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
Keyword Cannibalization Check
Identify queries where multiple pages on the same site are competing for rankings.
Steps
- Call
list_propertiesto confirm the exactsite_url. - Prefer
gsc_build_cannibalization_decision_queuefor the requested date range. Use defaults unless the user asks for different thresholds. - Treat the returned queue as a top-row Search Analytics sample, not all query+page combinations.
- Review candidates where a query has two or more distinct pages in the returned rows.
- For each case, use the queue's page metrics, winning-page heuristic, losing pages, impact score, confidence, warnings, limitations, and provenance.
- Sort and prioritize using the returned action item order unless the user asks for a different view.
- If the new queue tool is unavailable, fall back to
get_advanced_search_analyticswithdimensions=query,pageandrow_limit=500or the highest supported row limit, then group by query client-side.
Output format
For each cannibalization case:
- Query: the competing keyword
- Pages: list each URL with its metrics
- Severity: High / Medium / Low based on impressions at stake
- Recommendation: explain the queue's winner heuristic, then require manual SERP, business-intent, canonical, internal-link, and conversion review before suggesting consolidation, content updates, canonicals, redirects, or merges
Present as a markdown table followed by a prioritized action list.
Note: This is a sampled diagnostic based on the rows returned by Search Analytics. It can reveal likely cannibalization, but it is not proof and is not a guaranteed complete export of every competing page for every query.
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 · 32 lines · 37 tokens per session scan A e560d0b151b2
cannibalization-check is a skill published in the GitHub repository shutovdef-dotcom/google-search-console-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 404 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…
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…