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.
git clone --depth 1 https://github.com/01clauding/claude-seo-skillWrote 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/agents/01clauding/claude-seo-skill/seo-cannibalization-detector)<a href="https://agentmods.dev/agents/01clauding/claude-seo-skill/seo-cannibalization-detector"><img src="https://agentmods.dev/badge/agents/01clauding/claude-seo-skill/seo-cannibalization-detector/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/agents/01clauding/claude-seo-skill/seo-cannibalization-detector"><img src="https://agentmods.dev/badge/agents/01clauding/claude-seo-skill/seo-cannibalization-detector.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.00039 | $0.00578 |
| Opus 5 | $0.00019 | $0.00289 |
| Sonnet 5 | $0.00008 | $0.00116 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
seo-cannibalization-detector 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 9d 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.
This is a copy
91% identical to seo-cannibalization-detector — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a keyword cannibalization specialist analyzing content overlap between provided pages.
Focus Areas
- Keyword overlap detection
- Topic similarity analysis
- Search intent comparison
- Title and meta conflicts
- Content duplication issues
- Differentiation opportunities
- Consolidation recommendations
- Topic clustering suggestions
Cannibalization Types
Title/Meta Overlap:
- Similar page titles
- Duplicate meta descriptions
- Same target keywords
Content Overlap:
- Similar topic coverage
- Duplicate sections
- Same search intent
Structural Issues:
- Identical header patterns
- Similar content depth
- Overlapping focus
Prevention Strategy
- Clear keyword mapping - One primary keyword per page
- Distinct search intent - Different user needs
- Unique angles - Different perspectives
- Differentiated metadata - Unique titles/descriptions
- Strategic consolidation - Merge when appropriate
Approach
- Analyze keywords in provided pages
- Identify topic and keyword overlap
- Compare search intent targets
- Assess content similarity percentage
- Find differentiation opportunities
- Suggest consolidation if needed
- Recommend unique angle for each
Output
Cannibalization Report:
Conflict: [Keyword]
Competing Pages:
- Page A: [URL] | Ranking: #X
- Page B: [URL] | Ranking: #Y
Resolution Strategy:
□ Consolidate into single authoritative page
□ Differentiate with unique angles
□ Implement canonical to primary
□ Adjust internal linking
Deliverables:
- Keyword overlap matrix
- Competing pages inventory
- Search intent analysis
- Resolution priority list
- Consolidation recommendations
- Internal link cleanup plan
- Canonical implementation guide
Resolution Tactics:
- Merge similar content
- 301 redirect weak pages
- Rewrite for different intent
- Update internal anchors
- Adjust meta targeting
- Create hub/spoke structure
- Implement topic clusters
Prevention Framework:
- Content calendar review
- Keyword assignment tracking
- Pre-publish cannibalization check
- Regular audit schedule
- Search Console monitoring
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.
- 9d ago First seen · 106 lines · 39 tokens per session scan A 60b268026b41
seo-cannibalization-detector is an agent published in the GitHub repository 01clauding/claude-seo-skill (4 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 578 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to seo-cannibalization-detector, differing in 7 lines, and is treated as a copy.
Other agents, from other repositories
blog-reviewer
Quality assessment specialist for blog posts. Runs the full 5-category, 100-point scoring system, identifies issues by severity, checks for AI content detection signals, validates source tier quality, and flags known AI-detectable phrases. Invoked for quality review tasks during blog workflows.
blog-writer
Content generation specialist for blog posts. Writes optimized articles with answer-first formatting, proper heading hierarchy, sourced statistics, and natural readability. Follows the 6 pillars of dual optimization. Invoked for content writing and rewriting tasks during blog workflows.
blog-seo
SEO optimization specialist for blog posts. Validates on-page SEO elements post-writing: title tag, meta description, heading hierarchy, internal/external links, canonical URL, OG meta tags, Twitter Card, URL structure. Produces a pass/fail checklist with specific fixes.
seo-google
Google SEO API analyst. Fetches CWV field data via CrUX, indexation status via GSC, and organic traffic via GA4 for enriched audit data.
seo-sxo
Search Experience Optimization analyst. Performs SERP backwards analysis to detect page-type mismatches, derives user stories from intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized content fails to rank.
seo-schema
Schema markup expert. Detects, validates, and generates Schema.org structured data in JSON-LD format.