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/deliverable)<a href="https://agentmods.dev/commands/mizukaizen/hive-doctrine-mcp/deliverable"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/deliverable/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/deliverable"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/deliverable.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.00439 |
| Opus 5 | $0.00000 | $0.00219 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
deliverable 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
/deliverable
Generate a structured client deliverable from analysis work.
Usage
/deliverable "<deliverable title>" [--type report|memo|presentation] [--audience executive|technical|mixed]
Behaviour
1. Gather Context
- Scan the
analysis/directory for completed analyses. - Scan the
scope/engagement-brief.mdfor objectives and deliverable list. - Identify which deliverable this corresponds to and update its status.
2. Generate Document
Create the deliverable in deliverables/ with the appropriate structure:
For reports (default):
# [Title]
**Date:** [today]
**Classification:** Confidential — [Client Name] Only
**Version:** 1.0 — Draft
---
## Executive Summary
[One page maximum. Lead with the recommendation.]
## Context
[Why this engagement exists. What triggered it.]
## Approach
[Methodology used. Data sources. Limitations.]
## Findings
### Finding 1: [Theme]
[Evidence-based finding with source citations]
### Finding 2: [Theme]
[Evidence-based finding with source citations]
## Recommendations
1. **[Action]** — [Owner] by [date]. Expected impact: [quantified where possible].
2. **[Action]** — [Owner] by [date]. Expected impact: [quantified where possible].
## Next Steps
- [ ] [Immediate action]
- [ ] [Follow-up action]
## Appendices
### A. Methodology
### B. Data Sources
### C. Detailed Analysis
For memos: Shorter format — situation, complication, resolution structure.
For presentations: Slide-by-slide outline with key message per slide and supporting data points.
3. Quality Check
After generating, verify:
- Every finding cites a source
- Every recommendation has an owner and timeline
- Executive summary is comprehensible standalone
- Run confidentiality hook
4. Output
Display the deliverable path and a summary of contents. Ask the user to review before marking as final.
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 · 77 lines · 0 tokens per session scan A 17cf7358e8a5
deliverable 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 439 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
research-doc
Deep document research with evidence tiers and cross-referencing.
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 ].
mega-status
Show detailed status of mega-plan execution including feature progress and story completion. Usage: /plan-cascade:mega-status.
mega-edit
Edit the mega-plan interactively. Add, remove, or modify features. Usage: /plan-cascade:mega-edit.
edit
Edit the current PRD in your default editor. Opens prd.json, validates after saving, and re-displays review. Supports adding/removing stories, changing priorities, and modifying dependencies.
hybrid-manual
Load an existing PRD file and enter review mode. Supports JSON format with stories, priorities, dependencies, and acceptance criteria.