seo-content-planner

seo-content-planner is a command for Claude Code from maigentic/stratarts. It costs 39 tokens per session (15,744 once invoked), scanned A, original, MIT.

A planning command for improving a website’s visibility in search engines. It covers target search terms, groups related topics, technical checks, page-writing guidance, and a 90-day publishing plan.

In plain words
What is it for?
Use it to plan keywords and topic groups, review technical and on-page SEO, schedule content, plan link-building activities, and define success measures.
Why use it?
It organizes scattered SEO work into one strategy and makes it clearer what to publish, improve, and measure. It also helps identify technical and link-building work that can affect search traffic.

Command for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Part of the stratarts plugin — 27 commands shipped together

Good fit Use it to plan keywords and topic groups, review technical and on-page…

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/maigentic/stratarts/seo-content-planner
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/maigentic/stratarts

Made for: Claude Code.

Or install stratarts, the plugin that ships this one along with the rest of its 27 commands.

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-content-planner

README.md
[![agentmods](https://agentmods.dev/badge/commands/maigentic/stratarts/seo-content-planner.svg)](https://agentmods.dev/commands/maigentic/stratarts/seo-content-planner)
Your own site
<a href="https://agentmods.dev/commands/maigentic/stratarts/seo-content-planner"><img src="https://agentmods.dev/badge/commands/maigentic/stratarts/seo-content-planner.svg" alt="Measured on agentmods" height="20"></a>
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 15,744 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.00039 $0.15744
Opus 5 $0.00019 $0.07872
Sonnet 5 $0.00008 $0.03149
Haiku 4.5 $0.00004 $0.01574

Measured 7d ago against content hash 65b4d51716cd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

seo-content-planner 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 7d 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.

stratarts/commands/seo-content-planner.md · 1,994 lines

How it starts

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

SEO Content Planner

Step 0: Pre-Generation Verification

Before generating any output, verify these template requirements:

Template Location

  • Skeleton Template: html-templates/seo-content-planner.html
  • Test Output Reference: skills/marketing-growth/seo-content-planner/test-template-output.html

Required Placeholders to Replace

  • {{PRODUCT_NAME}} - Business/product name
  • {{SUBTITLE}} - Strategy summary tagline
  • {{DATE}} - Generation date
  • {{KEYWORD_COUNT}} - Total target keywords
  • {{CLUSTER_COUNT}} - Number of content clusters
  • {{INTERPRETATION_TITLE}} - Score interpretation headline
  • {{INTERPRETATION_TEXT}} - Detailed score explanation
  • {{VERDICT}} - Overall assessment badge
  • {{GOALS_DESCRIPTION}} - Goals section intro text
  • {{GOAL_CARDS}} - 3 goal cards HTML
  • {{KEYWORD_ROWS}} - Keyword table rows HTML
  • {{CLUSTER_CARDS}} - Content cluster cards HTML
  • {{TECH_CARDS}} - Technical SEO audit cards HTML
  • {{GUIDELINE_CARDS}} - On-page optimization guideline cards HTML
  • {{CALENDAR_MONTHS}} - 90-day content calendar HTML
  • {{LINKBUILDING_CARDS}} - Link building strategy cards HTML
  • {{METRIC_CARDS}} - Success metric cards HTML
  • {{ROADMAP_PHASES}} - Implementation roadmap phases HTML
  • {{CONTEXT_SIGNATURE}} - Unique session identifier

Chart Data Placeholders

  • {{DIFFICULTY_LABELS}} - Keyword difficulty labels (Easy, Medium, Hard)
  • {{DIFFICULTY_DATA}} - Count of keywords per difficulty level
  • {{INTENT_LABELS}} - Search intent labels
  • {{INTENT_DATA}} - Count of keywords per intent type
  • {{CLUSTER_LABELS}} - Content cluster names
  • {{CLUSTER_PLANNED_DATA}} - Planned articles per cluster
  • {{CLUSTER_PUBLISHED_DATA}} - Published articles per cluster
  • {{PROJECTION_DATASETS}} - Traffic and rankings projection data

Canonical CSS Patterns (MUST match exactly)

  • Header: header { background: #0a0a0a; padding: 0; ... } + .header-content { ... max-width: 1600px; background: linear-gradient(135deg, #10b981 0%, #14b8a6 100%); padding: 4rem 4rem 3rem 4rem; ... }
  • Score Banner: .score-banner { background: #0a0a0a; padding: 0; ... } + .score-container { display: grid; grid-template-columns: auto 1fr auto; ... max-width: 1600px; ... }
  • Footer: footer { background: #0a0a0a; ... } + .footer-content { max-width: 1600px; ... }

Read the full file on GitHub · 1,994 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. 7d ago First seen · 1,994 lines · 39 tokens per session scan A 65b4d51716cd

Subscribe to this mod's changes

seo-content-planner is a command published in the GitHub repository maigentic/stratarts (39 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 15,744 once invoked, about $0.0002 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.