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/retro)<a href="https://agentmods.dev/commands/mizukaizen/hive-doctrine-mcp/retro"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/retro/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/retro"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/retro.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.00425 |
| Opus 5 | $0.00000 | $0.00212 |
| Sonnet 5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
retro 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 10d 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: /retro
Weekly retrospective for solo founders. Run this every Friday.
Usage
/retro
Process
Step 1: What Shipped This Week
Review git commits and changelog entries from the past 7 days. List everything that went to production, grouped by feature or area.
git log --oneline --since="7 days ago" --no-merges
Step 2: What Got Blocked
Identify anything that was planned but did not ship. For each blocked item:
- What was the blocker?
- Was it technical, motivational, or scope-related?
- Is it still worth doing next week?
Step 3: Metrics Check
Review the key metrics for the week (if METRICS.md exists):
- Users (new, active, churned)
- Revenue (new MRR, total MRR)
- Conversion rate changes
- Any metric that moved more than 10% in either direction
Step 4: What to Change
Based on the above, recommend 1-2 process changes for next week. Keep it concrete:
- "Reduce scope on feature X to just the core flow"
- "Stop checking analytics more than once per day"
- "Time-box debugging to 30 minutes, then ask for help"
Step 5: Next Week's Focus
Pick the single most important thing to ship next week. Write it as a one-sentence goal. Everything else is secondary.
Output Format
Save the retro to docs/retros/retro-[YYYY-MM-DD].md with all five sections.
Rules
- Be honest, not kind. If nothing shipped, say so. If the founder is stuck in a loop, call it out.
- Do not let retros become planning sessions. The output is reflection and one clear focus for next week.
- If this is the third retro in a row where the same item is blocked, escalate: "This has been blocked for 3 weeks. Either solve it this week or kill it."
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.
- 10d ago First seen · 51 lines · 0 tokens per session scan A d140de7bb2c3
retro 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 425 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.
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.
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.