seomachine: Command for Claude Code

.claude/commands/cluster.md

cluster is a command for Claude Code from TheCraigHewitt/seomachine. It costs 0 tokens per session (2,915 once invoked), scanned A, original, MIT.

A command for planning a topic cluster: a main guide supported by related articles that link to one another. It uses keyword research and existing research files to define the articles and their creation order.

In plain words
What is it for?
Use it to define a main SEO guide, plan 8–12 supporting articles, map internal links, review existing research, and sequence content creation.
Why use it?
It turns a broad subject into an organised content plan and shows which pages should link together, reducing gaps and disconnected articles.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is TheCraigHewitt/seomachine's own configuration. It tells Claude Code how to work on seomachine itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything seomachine configures →

About the project

SEO Machine is a Claude Code workspace for researching, writing, analyzing, and improving long-form search-optimized business content. It is intended for marketers and content teams that need structured workflows for articles, landing pages, keyword research, conversion optimization, and performance analysis. Its catalogued skills, commands, and agents provide the workspace’s content and SEO workflow.

TheCraigHewitt/seomachine · 7,407 stars · on GitHub · seomachine.io

Reuse

Borrowing it

Nothing to install: this file belongs to TheCraigHewitt/seomachine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/TheCraigHewitt/seomachine/main/.claude/commands/cluster.md
Clone the repo
git clone --depth 1 https://github.com/TheCraigHewitt/seomachine

Made for: Claude Code.

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 cluster

README.md
[![agentmods](https://agentmods.dev/badge/commands/thecraighewitt/seomachine/cluster.svg)](https://agentmods.dev/commands/thecraighewitt/seomachine/cluster)
Your own site
<a href="https://agentmods.dev/commands/thecraighewitt/seomachine/cluster"><img src="https://agentmods.dev/badge/commands/thecraighewitt/seomachine/cluster.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,915 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 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.1 $0.00000 $0.02915
Opus 5 $0.00000 $0.01458
Sonnet 5 $0.00000 $0.00583
Haiku 4.5 $0.00000 $0.00292

Measured 8d ago against content hash 2352542f8877, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • cluster — 100% identical, 0 lines differ
.claude/commands/cluster.md · 362 lines

How it starts

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

Cluster Command

Build a complete topic cluster strategy with pillar page definition, 8-12 supporting articles, internal linking map, and creation sequence.

Usage

/cluster [topic]

Examples:

  • /cluster "content marketing"
  • /cluster "podcast monetization"
  • /cluster "remote team management"

Process

Step 1: Gather Existing Data

Check for existing research that informs this cluster:

  1. Search research/ for any existing /research-topics output:
    Glob: research/topic-clusters-*.md
    
  2. Search for any existing research on this topic:
    Glob: research/*[topic-slug]*.md
    
  3. If found, extract:
    • Authority score for this topic area
    • Keywords already ranking
    • Coverage gaps identified
    • Any SERP analysis already done

Document what exists vs. what needs fresh research.

Step 2: Keyword Research

Build the complete keyword landscape for this topic.

  1. DataForSEO Keyword Ideas

    python3 -c "
    import sys; sys.path.insert(0, 'data_sources/modules')
    from dataforseo import DataForSEOClient
    client = DataForSEOClient()
    results = client.get_keyword_ideas('$ARGUMENTS')
    for kw in sorted(results, key=lambda x: x.get('search_volume', 0), reverse=True)[:30]:
        print(f\"{kw.get('keyword', 'N/A')} | Vol: {kw.get('search_volume', 'N/A')} | Diff: {kw.get('keyword_difficulty', 'N/A')} | CPC: {kw.get('cpc', 'N/A')}\")
    "
    
  2. DataForSEO Questions

    python3 -c "
    import sys; sys.path.insert(0, 'data_sources/modules')
    from dataforseo import DataForSEOClient
    client = DataForSEOClient()
    results = client.get_questions('$ARGUMENTS')
    for q in results[:15]:
        print(f\"{q.get('keyword', 'N/A')} | Vol: {q.get('search_volume', 'N/A')}\")
    "
    
  3. WebSearch for Additional Keywords

    WebSearch: "[topic] guide" site:ahrefs.com OR site:semrush.com OR site:moz.com
    WebSearch: "[topic] related keywords" OR "[topic] subtopics"
    
  4. Group Keywords into Tiers

    • Pillar-level: Broad, high-volume (1000+ searches/mo), competitive
    • Supporting-level: Specific subtopics, medium volume (100-1000/mo)
    • Long-tail: Very specific queries, low volume (<100/mo), low competition

Read the full file on GitHub · 362 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. 8d ago First seen · 362 lines · 0 tokens per session scan A 2352542f8877

Subscribe to this mod's changes

cluster is a command published in the GitHub repository TheCraigHewitt/seomachine (7,407 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,915 tokens. 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.