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 skills add mizukaizen/hive-doctrine-mcp --skill seo-optimisationgit 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/skills/mizukaizen/hive-doctrine-mcp/seo-optimisation)<a href="https://agentmods.dev/skills/mizukaizen/hive-doctrine-mcp/seo-optimisation"><img src="https://agentmods.dev/badge/skills/mizukaizen/hive-doctrine-mcp/seo-optimisation/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/skills/mizukaizen/hive-doctrine-mcp/seo-optimisation"><img src="https://agentmods.dev/badge/skills/mizukaizen/hive-doctrine-mcp/seo-optimisation.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.00778 |
| Opus 5 | $0.00000 | $0.00389 |
| Sonnet 5 | $0.00000 | $0.00156 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
seo-optimisation 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: SEO Optimisation
Use when optimising existing content for search. Analyses keyword placement, meta tags, internal linking structure, readability, and competitive positioning. Produces specific, actionable improvements.
Trigger
Invoke this skill when the user wants to improve an existing post's search ranking, when the /seo-check command runs, or when a post has been published for 30+ days without ranking.
Process
1. Content Audit
Read the content and extract:
- Current title and meta description
- All headings with hierarchy
- Word count and reading time
- All links (internal and external)
- All images and their alt text
- Primary keyword (from frontmatter or inferred)
2. Keyword Analysis
Placement Check:
- Title: Does it contain the primary keyword naturally?
- First 100 words: Does the keyword appear early?
- H2 headings: Is the keyword in at least one H2?
- Meta description: Is the keyword included?
- Alt text: Does at least one image alt text include the keyword?
- URL slug: Is the keyword in the URL?
Density Check:
- Count keyword occurrences vs total words
- Target range: 0.5%-1.5%
- Below 0.5%: Content may not signal relevance strongly enough
- Above 2.0%: Risk of keyword stuffing penalty
Semantic Keywords:
- Identify related terms that should appear in the content
- Check for natural inclusion of synonyms and related concepts
- Suggest additions where semantic coverage is thin
3. Technical SEO
Meta Tags:
- Title tag: Under 60 characters? Unique? Compelling?
- Meta description: 150-160 characters? Includes keyword? Creates curiosity?
- Open Graph tags: Present for social sharing?
Structure:
- Heading hierarchy correct (no skipped levels)?
- Content chunked into scannable sections?
- Table of contents warranted (for posts over 2,000 words)?
Links:
- Internal links: At least 2, pointing to relevant related content
- External links: At least 1 authoritative source
- Anchor text: Descriptive (not "click here" or "this article")
- Broken links: Any obvious dead links?
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 · 97 lines · 0 tokens per session scan A dfe6fac849eb
seo-optimisation is a skill 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 778 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 skills, from other repositories
coding-agents-farm
To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.
brain-in-the-fish
Universal document evaluation engine — evaluate any document against any criteria using cognitively-modelled AI agents with ontology-grounded scoring.
superagenticmcp
SuperAgenticMCP — the switchboard for your agent swarm. MCP-native router and multi-agent control plane that plans tasks, routes tool calls to racked MCP servers by capability and latency, streams execution, and files results into a memory-scope graph. Use when the user needs multi-agent orchestration over MCP, a…
go-best-practices
Go coding best practices. Use when writing or reviewing Go code. Covers error handling, concurrency, and idiomatic patterns.
java-best-practices
Java coding best practices. Use when writing or reviewing Java code (17+). Covers modern features, error handling, and patterns.
python-best-practices
Python coding best practices. Use when writing or reviewing Python code. Covers type hints, error handling, and common patterns.