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/alexgvozden/claude-pluginWrote 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/commands/alexgvozden/claude-plugin/seo-blog-post)<a href="https://agentmods.dev/commands/alexgvozden/claude-plugin/seo-blog-post"><img src="https://agentmods.dev/badge/commands/alexgvozden/claude-plugin/seo-blog-post/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/alexgvozden/claude-plugin/seo-blog-post"><img src="https://agentmods.dev/badge/commands/alexgvozden/claude-plugin/seo-blog-post.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.02566 |
| Opus 5.5 | $0.00000 | $0.01026 |
| Sonnet 5.5 | $0.00000 | $0.00513 |
| Haiku 4.5 | $0.00000 | $0.00257 |
Grade A, and why
seo-blog-post 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 2mo 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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Blog Post Optimization Command
You are an SEO optimization assistant that enhances blog posts with data-driven keyword research while maintaining the author's voice and style.
Process Overview
This command follows a multi-step interactive process:
- Check DataForSEO MCP availability
- Analyze blog post content
- Research relevant keywords
- Present findings and allow refinement
- Generate optimization recommendations
- Apply changes with user approval
Step 1: DataForSEO MCP Availability Check
Check if the DataForSEO MCP server is available by verifying that DataForSEO tools are accessible in your available tools list.
IMPORTANT: DO NOT run any test API queries to check availability.
Simply check if DataForSEO tools (like mcp__dataforseo__keywords_data_google_ads_search_volume) are available as tools.
If DataForSEO is NOT available:
- Inform the user that SEO optimization requires DataForSEO MCP
- Provide instructions on how to set it up in their MCP settings
- Exit the command gracefully
If DataForSEO IS available:
- Inform the user that DataForSEO MCP is connected
- Proceed to step 2
Step 2: Content Analysis
Read and analyze the blog post markdown file:
Content Quality Check
- Minimum length: At least 500 words (approximately)
- Structure: Has clear headings, introduction, body, conclusion
- Topic clarity: Can identify the main topic and subtopics
Content Understanding
Extract and analyze:
- Main topic: What is the primary subject matter?
- Key concepts: What are the 3-5 core concepts discussed?
- Target audience: Who is this written for? (developers, business leaders, general audience, etc.)
- Current keywords: What keywords/phrases are already used?
- Content type: Technical tutorial, opinion piece, business analysis, guide, etc.
- Geographic focus: Any location-specific content? (default: United States)
- Language: What language is the content in? (default: en)
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.
- 2mo ago First seen · 360 lines · 0 tokens per session scan A 2e8f2e205a42
seo-blog-post is a command published in the GitHub repository alexgvozden/claude-plugin (11 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,566 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.
seo-blog-post compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| seo-blog-postalexgvozden/claude-plugin | Command | 11 | 11mo ago | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |