topic-clusters

A command for analyzing content clusters: groups of related web pages connected around a main pillar page. It examines links between pages and suggests topics and internal-linking improvements.

In plain words
What is it for?
Use it to inspect existing clusters, find new long-tail content opportunities, and plan links between pillar pages and supporting articles.
Why use it?
It shows where a site's related content is disconnected or incomplete, which can make the site's coverage and navigation harder to improve.

Command

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.

agentmods
npx agentmods add commands/huifer/claude-code-seo/topic-clusters
Clone the repo
git clone --depth 1 https://github.com/huifer/claude-code-seo
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 225 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00011 $0.00225
Opus 5 $0.00005 $0.00112
Sonnet 5 $0.00002 $0.00045
Haiku 4.5 $0.00001 $0.00022

Measured 2d ago against content hash de941a02b965, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

topic-clusters 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 2d 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.

commands/topic-clusters.md · 35 lines

What it actually says

分析内容集群结构,提供优化建议。识别现有的内容集群、分析集群内容的链接关系、建议新的集群内容机会、优化内部链接结构、提升话题权威性。

参数

  • --analyze: 分析现有集群结构
  • --suggest: 建议新集群内容主题

集群策略

每个支柱页面关联 5-10 篇集群内容,所有集群内容链接回支柱页面,集群内容之间相互链接,覆盖长尾关键词。

使用示例

/topic-clusters --analyze

分析现有内容集群的结构和链接关系。

/topic-clusters --suggest

建议新的集群内容主题和结构。

相关命令

  • /pillar-pages - 支柱页面分析
  • /content-strategy - 内容策略
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. 2d ago First seen · 35 lines · 0 tokens per session scan A de941a02b965

Subscribe to this mod's changes

topic-clusters is a command published in the GitHub repository huifer/claude-code-seo (110 stars, last pushed 8mo ago), licensed MIT. It adds 11 tokens to every session and 225 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.

Related

Other commands, from other repositories