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 JakeLabate/Claude-SEO-Skills --skill keyword-cannibalization-auditgit clone --depth 1 https://github.com/JakeLabate/Claude-SEO-SkillsWrote 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/jakelabate/claude-seo-skills/keyword-cannibalization-audit)<a href="https://agentmods.dev/skills/jakelabate/claude-seo-skills/keyword-cannibalization-audit"><img src="https://agentmods.dev/badge/skills/jakelabate/claude-seo-skills/keyword-cannibalization-audit/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/jakelabate/claude-seo-skills/keyword-cannibalization-audit"><img src="https://agentmods.dev/badge/skills/jakelabate/claude-seo-skills/keyword-cannibalization-audit.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.00110 | $0.01223 |
| Opus 5 | $0.00055 | $0.00611 |
| Sonnet 5 | $0.00022 | $0.00245 |
| Haiku 4.5 | $0.00011 | $0.00122 |
Grade A, and why
keyword-cannibalization-audit 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 12d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Keyword Cannibalization Audit
Audit a website for pages that compete with each other for the same query, and produce an actionable report. Findings are candidates to confirm — some overlap is legitimate; this skill surfaces the clusters and recommends a hierarchy.
When to use this skill
Use this skill when the user asks to:
- Audit or fix keyword cannibalization
- Find pages competing for the same keyword / query
- Decide which page should rank for a topic and what to do with the rest
- Review overlapping or competing content
Inputs to collect
- Site URL or URL list — a live site root to crawl (auto-seeds from
/sitemap.xml), or a text file with--url-list. - Scope — pages to crawl (default 500,
--max-pages). - Brand suffix — e.g.
"| Acme Co"so brand words don't inflate title similarity (--brand-suffix). - Overlap threshold — Jaccard similarity to flag competing pages (default
0.6,
--overlap).
Workflow
Step 1: Crawl and capture target signals
Use scripts/extract_targets.py:
python3 scripts/extract_targets.py https://example.com --max-pages 500 --output target_inventory.json
# already crawled once (e.g. in a full SEO audit)? skip the crawl and reuse the shared cache:
# python3 scripts/fetch_pages.py https://example.com --output page_cache.json
# python3 scripts/extract_targets.py --from-cache page_cache.json --output target_inventory.json
For each page it records title, H1, meta description, noindex, word count, and the top body keywords by frequency.
Step 2: Run the audit checks
python3 scripts/audit_cannibalization.py target_inventory.json --brand-suffix "| Acme Co" --overlap 0.6 --output audit_report.json
Step 3: Evaluate the audit checks
Evaluate each check in references/audit-checks.md. Core checks:
| Check | Severity |
|---|---|
| Duplicate title target | High |
| Overlapping target cluster (keyword signatures) | Medium |
| Shared primary keyword (title bigram) | Low |
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.
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.
- 12d ago First seen · 112 lines · 110 tokens per session scan A 54e3807cf9a6
keyword-cannibalization-audit is a skill published in the GitHub repository JakeLabate/Claude-SEO-Skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 110 tokens to every session and 1,223 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
seo-audit
A checklist-based SEO review for a website. SEO, or search engine optimization, is the work of improving a site so search engines can understand and rank it.
fire-your-seo-agency
A procedure for improving how a website appears in search engines and how AI answer systems find and cite it. It covers search, answer-engine, generative-AI, and Naver visibility.
geo-loop
Run one bounded eGEOagents loop iteration over a workspace domain - read the charter and fresh collector data, do ONE unit of work, write substrate artifacts, append one Timeline entry and one LOG line. Use for loop mode, /geo:loop, scheduled GEO runs, or continuous monitoring.
content-scoring
Score content against the 10 GEO criteria with evidence and prioritized fixes. Use when users ask to score, rate, evaluate, or estimate ranking strength.
competitive-analysis
Analyze AI-search competitors for a query and recommend ranking strategy. Use when users ask competitor analysis, who ranks, or competitive landscape.
validation-doctor
Check Brave Search and Chrome DevTools MCP availability and provide exact setup snippets. Use when validation dependencies are missing or uncertain.