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/lit-review)<a href="https://agentmods.dev/commands/mizukaizen/hive-doctrine-mcp/lit-review"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/lit-review/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/lit-review"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/lit-review.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.00476 |
| Opus 5 | $0.00000 | $0.00238 |
| Sonnet 5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
lit-review 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.
What it actually says
/lit-review
Conduct a systematic literature review with structured synthesis.
Usage
/lit-review "<research question>" [--databases "DB1, DB2"] [--years "2020-2025"] [--max-sources N]
Behaviour
1. Define Search Strategy
Create literature/search-strategy.md with:
# Search Strategy
## Research Question
[From argument, reformulated using PICO framework if applicable]
## Search Terms
- Primary: [key terms]
- Synonyms: [alternative terms]
- Boolean: [full search string]
## Databases
[From --databases or default: "Specify relevant databases for your field"]
## Date Range
[From --years or "No restriction"]
## Inclusion Criteria
1. Published in peer-reviewed journal
2. Available in English
3. [Field-specific criteria]
## Exclusion Criteria
1. Conference abstracts only (no full text)
2. [Field-specific criteria]
2. Structure for Paper Collection
Create the directory structure:
literature/
├── search-strategy.md
├── screening-log.md
├── included-papers/
│ └── [paper-key].md (one file per included paper)
└── synthesis.md
3. Paper Extraction Template
For each included paper, create a structured note:
# [Author (Year)] — [Short Title]
## Citation
[Full APA citation]
## Study Design
[RCT / Cohort / Cross-sectional / etc.]
## Sample
[N, demographics, setting]
## Key Findings
- [Finding 1]
- [Finding 2]
## Methodology Quality
[High / Medium / Low — with justification]
## Relevance to Our Question
[Direct / Indirect — explanation]
## Limitations Noted
- [Limitation 1]
4. Synthesis
Generate literature/synthesis.md with:
- Thematic grouping of findings
- Areas of agreement and contradiction
- Evidence strength assessment per theme
- Identified gaps
- Implications for the current study
5. Output
Display summary statistics (papers screened, included, excluded with reasons) and the key themes identified.
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 d5a2542eda67
lit-review 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 476 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.