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/validate)<a href="https://agentmods.dev/commands/mizukaizen/hive-doctrine-mcp/validate"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/validate/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/validate"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/validate.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.00443 |
| Opus 5 | $0.00000 | $0.00221 |
| Sonnet 5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
validate 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 8d 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.
What it actually says
Command: /validate
Run a structured idea validation before committing to building anything.
Usage
/validate [idea description]
Process
When this command is invoked, follow these steps in order:
Step 1: Problem Statement
Ask the founder to articulate the problem in one sentence. If they cannot, the idea is not ready. Format: "[Who] struggles with [problem] because [reason]."
Step 2: Market Sizing
Estimate TAM, SAM, and SOM:
- TAM (Total Addressable Market): How many people in the world have this problem?
- SAM (Serviceable Addressable Market): How many of those can you realistically reach?
- SOM (Serviceable Obtainable Market): How many of those will you capture in year 1?
Use publicly available data. If no data exists, flag that as a risk.
Step 3: Competitor Landscape
Search for existing solutions. For each competitor found:
- Name and URL
- Pricing model
- Key differentiator
- Obvious weakness
If there are zero competitors, that is a red flag — not a green one. Either the market does not exist or you have not looked hard enough.
Step 4: Willingness to Pay (WTP)
Assess whether people will pay for this:
- Are there paid alternatives? What do they charge?
- Is this a painkiller (must-have) or a vitamin (nice-to-have)?
- What is the founder's target price point? Is it realistic given the competitive landscape?
Step 5: Verdict
Provide a clear GO / NO-GO / NEEDS MORE DATA recommendation with reasoning.
Output Format
Save the validation to docs/validations/[idea-slug]-validation.md with all five sections.
Rules
- Do not sugar-coat results. A "NO-GO" is more valuable than a false "GO."
- If the founder pushes back on a NO-GO, ask them what new evidence would change the verdict. Vibes are not evidence.
- Time-box the entire validation to 15 minutes of active work.
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.
- 8d ago First seen · 53 lines · 0 tokens per session scan A 93af013ba6a0
validate 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 443 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.
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.
design-import
Import an external design document (Markdown, JSON, or HTML from Confluence/Notion) and convert it to designdoc.json format for Plan Cascade integration.