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/mizukaizen/hive-doctrine-mcpWrote 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/mizukaizen/hive-doctrine-mcp/seo-check)<a href="https://agentmods.dev/commands/mizukaizen/hive-doctrine-mcp/seo-check"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/seo-check/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/mizukaizen/hive-doctrine-mcp/seo-check"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/seo-check.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.00713 |
| Opus 5 | $0.00000 | $0.00357 |
| Sonnet 5 | $0.00000 | $0.00143 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
seo-check 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 11d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: /seo-check
Run an SEO analysis on existing content and provide actionable improvement recommendations.
Usage
/seo-check [file-path]
Process
Step 1: Read the Content
Load the specified file and extract:
- Title / H1
- Meta description (from frontmatter or first paragraph)
- All headings (H2, H3, H4)
- Word count
- Primary keyword (from frontmatter or inferred from title)
Step 2: Keyword Analysis
Check keyword placement:
| Location | Required | Found | Status |
|---|---|---|---|
| Title / H1 | Yes | [Yes/No] | [Pass/Fail] |
| First paragraph | Yes | [Yes/No] | [Pass/Fail] |
| At least one H2 | Yes | [Yes/No] | [Pass/Fail] |
| Meta description | Yes | [Yes/No] | [Pass/Fail] |
| Image alt text | Yes | [Yes/No] | [Pass/Fail] |
Calculate keyword density: Occurrences / total words. Target: 0.5%-1.5%. Flag if below 0.5% (underused) or above 2% (keyword stuffing).
Step 3: Structure Analysis
- Heading hierarchy: Is it correct (H1 > H2 > H3)? Are there skipped levels?
- Heading count: At least 3 H2 sections for posts over 1,000 words.
- Paragraph length: Flag any paragraph over 5 sentences.
- Content length: Is it competitive with top-ranking content for the target keyword?
Step 4: Link Analysis
- Internal links: Count and list. Target: at least 2 per post.
- External links: Count and list. Target: at least 1 authoritative source.
- Broken links: Check for obvious issues (404 patterns, dead domains).
Step 5: Meta Tags
- Title tag: Under 60 characters? Includes keyword?
- Meta description: 150-160 characters? Includes keyword? Compelling?
- URL slug: Short, descriptive, includes keyword?
Step 6: Generate Report
# SEO Analysis: [Post Title]
**Date:** [YYYY-MM-DD]
**Overall Score:** [X/10]
**Primary Keyword:** [keyword]
**Keyword Density:** [X]%
## Keyword Placement
[Table from Step 2]
## Issues Found
### Must Fix
1. [Issue and specific fix]
### Should Fix
1. [Issue and suggested improvement]
## Recommendations
1. [Specific, actionable recommendation]
2. [Specific, actionable recommendation]
3. [Specific, actionable recommendation]
## Comparison to Competitors
- Average competing content length: [X] words
- Your content length: [X] words
- Topics covered by competitors but missing from your content: [list]
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.
- 11d ago First seen · 87 lines · 0 tokens per session scan A 38e3309a52a5
seo-check is a command published in the GitHub repository mizukaizen/hive-doctrine-mcp (0 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 713 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-31.
Other commands, from other repositories
mega-approve
Approve the mega-plan and start feature execution. Creates worktrees and generates PRDs for each feature. Usage: /plan-cascade:mega-approve [--flow ] [--tdd ] [--confirm] [--no-confirm] [--spec ] [--first-principles] [--max-questions N] [--auto-prd] [--agent ] [--prd-agent ] [--impl-agent ].
auto
AI auto strategy executor. Analyzes task and automatically selects and executes the best strategy: direct execution, hybrid-auto PRD generation, hybrid-worktree isolated development, or mega-plan multi-feature orchestration.
design-generate
Generate a technical design document. Auto-detects level: project-level from mega-plan.json, or feature-level from prd.json. Provides architectural context for story execution.
design-review
Review and interactively edit the current designdoc.json. Displays the design document in a readable format and allows modifications to components, patterns, decisions, and story mappings.
resume
Auto-detect and resume any interrupted Plan Cascade task. Detects mega-plan, hybrid-worktree, or hybrid-auto context and routes to the appropriate resume command.
worktree
Start a new task in an isolated Git worktree for parallel multi-task development. Creates a task branch, worktree directory with planning files, and leaves the main directory untouched. Usage: /plan-cascade:worktree [task-name] [target-branch]. Example: /plan-cascade:worktree feature-login main.