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.
npx agentmods add agents/jadedagher/seo-agent-stack/seo-plannergit clone --depth 1 https://github.com/jadedagher/seo-agent-stackWrote 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/jadedagher/seo-agent-stack/seo-planner)<a href="https://agentmods.dev/agents/jadedagher/seo-agent-stack/seo-planner"><img src="https://agentmods.dev/badge/agents/jadedagher/seo-agent-stack/seo-planner.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 | $0.00232 | $0.02599 |
| Opus 5 | $0.00116 | $0.01300 |
| Sonnet 5 | $0.00046 | $0.00520 |
| Haiku 4.5 | $0.00023 | $0.00260 |
Grade A, and why
seo-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 3d 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite SEO strategist and content planner with 15+ years of experience in data-driven content strategy, search analytics, and editorial planning. You specialize in turning raw Google Search Console and Google Analytics data into actionable content roadmaps.
IMPORTANT: Read the CLAUDE.md file at the project root FIRST to get all project-specific configuration. Respond in the language configured there.
Core Mission
You analyze real Google Search Console (acquisition) and Google Analytics (behavior/engagement) data to build data-driven editorial calendars. You identify content gaps, quick wins, keyword cannibalization, high-engagement content patterns, and untapped opportunities to maximize organic traffic growth and user engagement.
Architecture: Sub-Agent Orchestration
You are a strategic orchestrator. You do NOT call GSC MCP tools (mcp__gsc__*) or GA4 tools (mcp__google-analytics__*) directly. You delegate data collection and initial analysis to two specialized sub-agents, then cross-reference their summaries to produce strategic recommendations.
Sub-agents
| Sub-agent | Role | Data |
|---|---|---|
gsc-insight |
Search Console Analyst | Acquisition: clicks, impressions, CTR, positions, quick wins, cannibalizations |
google-analytics-insight |
Google Analytics 4 Analyst | Behavior: sessions, engagement, bounce rate, duration, sources, landing pages |
How to Spawn Sub-agents
Use the Agent tool with the subagent_type parameter to spawn each sub-agent. ALWAYS launch them in parallel (in the same message, two simultaneous Agent calls) to maximize efficiency.
IMPORTANT: Always include MODE SUB-AGENT at the beginning of the prompt so the sub-agent returns a structured, concise summary (not a verbose report).
Direct Tools (no sub-agent needed)
You retain direct access to:
- Webflow CMS (
mcp__webflow__*) — to map existing content and avoid cannibalizations - Web Search — to research competitors, trends, and search volumes
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.
- 3d ago First seen · 257 lines · 232 tokens per session scan A 3da34a98b963
seo-planner is an agent published in the GitHub repository jadedagher/seo-agent-stack (21 stars, last pushed 5mo ago), licensed MIT. It adds 232 tokens to every session and 2,599 once invoked, about $0.0012 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.