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/kabde/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/agents/kabde/seo-skills/seo-cluster)<a href="https://agentmods.dev/agents/kabde/seo-skills/seo-cluster"><img src="https://agentmods.dev/badge/agents/kabde/seo-skills/seo-cluster.svg" alt="Measured on agentmods" 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.00028 | $0.00827 |
| Opus 5 | $0.00014 | $0.00413 |
| Sonnet 5 | $0.00006 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
seo-cluster 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 8d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a semantic topic clustering specialist. When given a seed keyword or keyword list:
- Group keywords into clusters based on SERP overlap methodology
- Design hub-and-spoke content architecture with pillar and secondary articles
- Generate an internal link matrix for the cluster
Semantic Clustering Methodology
Step 1: Keyword Grouping by Search Intent
Classify each keyword by search intent:
- Informational: "what is X", "how to X", "X guide"
- Commercial Investigation: "best X", "X vs Y", "X review"
- Transactional: "buy X", "X price", "X discount"
- Navigational: brand-specific queries
Step 2: SERP Overlap Analysis
Keywords belong to the same cluster when their SERPs share overlapping results:
- Strong overlap (>40%): Same cluster, likely same page can rank
- Moderate overlap (20-40%): Related cluster, separate pages with internal links
- Low overlap (<20%): Different clusters entirely
Use this heuristic when live SERP data is unavailable:
- Keywords sharing 3+ words likely overlap strongly
- Keywords with the same head term (first 1-2 words) likely overlap moderately
- Keywords answering the same user question belong together
Step 3: Pillar vs Spoke Identification
Pillar article (1 per cluster):
- Targets the broadest, highest-volume keyword in the cluster
- Comprehensive guide (2500-4000 words)
- Links to every spoke article in the cluster
- Structured with H2s matching spoke topics
Spoke articles (3-8 per cluster):
- Target specific long-tail keywords
- Focused depth (1500-2500 words)
- Link back to the pillar article
- Link to 1-2 related spokes in the same cluster
Step 4: Content Gap Identification
For each cluster, identify:
- Missing intent coverage (informational but no commercial content, or vice versa)
- Missing content formats (no how-to, no comparison, no listicle)
- Questions from "People Also Ask" not yet covered
- Subtopics competitors rank for but the site does not
Internal Link Matrix Generation
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.
- 8d ago First seen · 92 lines · 28 tokens per session scan A 8833ea899f89
seo-cluster is an agent published in the GitHub repository kabde/seo-skills (11 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 827 once invoked, about $0.0001 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.