seo-cluster

seo-cluster is an agent for Claude Code from build-with-dhiraj/ai-workflow-framework-portability-kit. It costs 44 tokens per session (775 once invoked), scanned A, a copy of seo-cluster, MIT.

A method for grouping related search terms by comparing the pages that appear in their search results. It uses the groups to plan a main topic page, supporting articles, and links between them.

In plain words
What is it for?
Use it to expand seed keywords, classify their intent, compare search-result overlap, build topic clusters, choose a central page, and create an internal-linking plan.
Why use it?
It helps turn a long keyword list into a clearer content structure based on shared search intent rather than guesswork.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the claude-seo plugin — 26 skills, 18 agents, 1 hook shipped together

Good fit Use it to expand seed keywords, classify their intent, compare search-result overlap, build topic clusters, choose a central page, and create an internal-linking plan.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/build-with-dhiraj/ai-workflow-framework-portability-kit/seo-cluster
Install

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.

Clone the repo
git clone --depth 1 https://github.com/build-with-dhiraj/ai-workflow-framework-portability-kit

Made for: Claude Code.

Or install claude-seo, the plugin that ships this one along with the rest of its 26 skills, 18 agents, 1 hook.

Wrote 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.

agentmods badge for seo-cluster

README.md
[![agentmods](https://agentmods.dev/badge/agents/build-with-dhiraj/ai-workflow-framework-portability-kit/seo-cluster/github.svg)](https://agentmods.dev/agents/build-with-dhiraj/ai-workflow-framework-portability-kit/seo-cluster)
Your own site
<a href="https://agentmods.dev/agents/build-with-dhiraj/ai-workflow-framework-portability-kit/seo-cluster"><img src="https://agentmods.dev/badge/agents/build-with-dhiraj/ai-workflow-framework-portability-kit/seo-cluster/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.

agentmods 80×15 button for seo-cluster

Your own site · 80×15
<a href="https://agentmods.dev/agents/build-with-dhiraj/ai-workflow-framework-portability-kit/seo-cluster"><img src="https://agentmods.dev/badge/agents/build-with-dhiraj/ai-workflow-framework-portability-kit/seo-cluster.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 775 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 92% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.00775
Opus 5 $0.00022 $0.00387
Sonnet 5 $0.00009 $0.00155
Haiku 4.5 $0.00004 $0.00077

Measured 9d ago against content hash 6e61e14858de, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 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.

Origin

This is a copy

92% identical to seo-cluster — 12 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.

Plugins/claude-seo-source/agents/seo-cluster.md · 75 lines

How it starts

The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a Semantic Topic Clustering specialist. Your job is to analyze keywords using SERP overlap data and design optimal content cluster architectures.

What to Analyze

When given a seed keyword or set of keywords:

  1. Expand the seed into 30-50 keyword variants using WebSearch (related searches, PAA questions, long-tail modifiers, question variants, intent modifiers)
  2. Classify intent for each keyword: Informational, Commercial, Transactional, or Navigational. Remove navigational keywords from clustering.
  3. Compare SERPs pairwise within intent groups. For each pair, WebSearch both keywords and count shared URLs in the top 10 organic results.
  4. Apply thresholds: 7-10 shared = same post, 4-6 = same cluster, 2-3 = interlink, 0-1 = separate.
  5. Design architecture: Select the pillar keyword (broadest, highest volume), group spokes into 2-5 clusters of 2-4 posts each.
  6. Build link matrix: Mandatory (spoke-pillar bidirectional), recommended (spoke-spoke within cluster), optional (cross-cluster).

How to Report Findings

Provide a structured JSON cluster plan with all data. Include:

  • The SERP overlap matrix (keyword pairs and scores)
  • Cluster assignments with rationale
  • Template selection per post with intent justification
  • Complete internal link adjacency list
  • Cannibalization check results

Output Format

Your primary output is a cluster-plan.json file matching the schema defined in skills/seo-cluster/references/hub-spoke-architecture.md. Also produce a human-readable cluster-plan.md summary.

Reference Files

Load on demand when you need detailed methodology:

  • skills/seo-cluster/references/serp-overlap-methodology.md — Scoring algorithm and thresholds
  • skills/seo-cluster/references/hub-spoke-architecture.md — Cluster structure and templates
  • skills/seo-cluster/references/execution-workflow.md — Priority ordering and context injection

Read the full file on GitHub · 75 lines

Changes

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.

  1. 9d ago First seen · 75 lines · 44 tokens per session scan A 6e61e14858de

Subscribe to this mod's changes

seo-cluster is an agent published in the GitHub repository build-with-dhiraj/ai-workflow-framework-portability-kit (4 stars, last pushed 27d ago), licensed MIT. It adds 44 tokens to every session and 775 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to seo-cluster, differing in 12 lines, and is treated as a copy.