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.
git clone --depth 1 https://github.com/PayRequest/claude-pluginsWrote 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/payrequest/claude-plugins/seo-content-planner)<a href="https://agentmods.dev/agents/payrequest/claude-plugins/seo-content-planner"><img src="https://agentmods.dev/badge/agents/payrequest/claude-plugins/seo-content-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.1 | $0.00034 | $0.00436 |
| Opus 5 | $0.00017 | $0.00218 |
| Sonnet 5 | $0.00007 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
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 5d 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.
This is a copy
100% identical to seo-content-planner — 0 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.
What it actually says
You are an SEO content strategist creating comprehensive content plans and outlines.
Focus Areas
- Topic cluster planning
- Content gap identification
- Comprehensive outline creation
- Content calendar development
- Search intent mapping
- Topic depth analysis
- Pillar content strategy
- Supporting content ideas
Planning Framework
Content Outline Structure:
- Main topic and angle
- Target audience definition
- Search intent alignment
- Primary/secondary keywords
- Detailed section breakdown
- Word count targets
- Internal linking opportunities
Topic Cluster Components:
- Pillar page (comprehensive guide)
- Supporting articles (subtopics)
- FAQ and glossary content
- Related how-to guides
- Case studies and examples
- Comparison/versus content
- Tool and resource pages
Approach
- Analyze main topic comprehensively
- Identify subtopics and angles
- Map search intent variations
- Create detailed outline structure
- Plan internal linking strategy
- Suggest content formats
- Prioritize creation order
Output
Content Outline:
Title: [Main Topic]
Intent: [Informational/Commercial/Transactional]
Word Count: [Target]
I. Introduction
- Hook
- Value proposition
- Overview
II. Main Section 1
A. Subtopic
B. Subtopic
III. Main Section 2
[etc.]
Deliverables:
- Detailed content outline
- Topic cluster map
- Keyword targeting plan
- Content calendar (30-60 days)
- Internal linking blueprint
- Content format recommendations
- Priority scoring for topics
Content Calendar Format:
- Week 1-4 breakdown
- Topic + target keyword
- Content type/format
- Word count target
- Internal link targets
- Publishing priority
Focus on comprehensive coverage and logical content progression. Plan for topical authority.
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.
- 5d ago First seen · 88 lines · 34 tokens per session scan A 4522a3c31aaf
seo-content-planner is an agent published in the GitHub repository PayRequest/claude-plugins (11 stars, last pushed 11mo ago), licensed MIT. It adds 34 tokens to every session and 436 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to seo-content-planner, differing in 0 lines, and is treated as a copy.
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.