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/draft-paper)<a href="https://agentmods.dev/commands/mizukaizen/hive-doctrine-mcp/draft-paper"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/draft-paper/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/draft-paper"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/draft-paper.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.00420 |
| Opus 5.5 | $0.00000 | $0.00168 |
| Sonnet 5.5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
draft-paper 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 1mo 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
/draft-paper
Draft a paper section following academic conventions.
Usage
/draft-paper --section "intro|methods|results|discussion|abstract" [--journal "<journal name>"] [--word-limit N]
Behaviour
1. Gather Context
- Read
literature/synthesis.mdfor background and citations (intro, discussion). - Read
analysis/outputs/for results and statistics (methods, results). - Read
analysis/preregistration.mdfor methodology details. - If
--journalis specified, adapt formatting to that journal's conventions.
2. Draft the Section
Generate the section following IMRaD conventions as defined in the writer agent's guidelines. Each section:
- Abstract — Structured: Background, Methods, Results, Conclusions. Typically 150-300 words.
- Introduction — Broad context to specific gap to hypothesis. Cite throughout.
- Methods — Reproducible detail. Past tense. Subheadings: Participants, Materials, Procedure, Analysis.
- Results — Pre-registered analyses first, then exploratory. APA-formatted statistics.
- Discussion — Summary, interpretation, comparison with literature, limitations, implications, conclusion.
3. Citation Check
After drafting, verify:
- Every factual claim has a citation.
- Every citation appears in the bibliography.
- No orphaned references (cited but not in text, or in text but not in reference list).
4. Output
Save to paper/draft-[section].md. Display the section with a word count and any citation warnings.
If the section references analyses not yet completed, flag them as "[PENDING: analysis of X required]" rather than fabricating results.
Notes
- Never fabricate results or statistics. If data is not available, mark the gap explicitly.
- When writing the discussion, present limitations as specific methodological points, not generic disclaimers.
- If a word limit is specified, prioritise content ruthlessly. Cut padding before cutting substance.
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.
- 1mo ago First seen · 48 lines · 0 tokens per session scan A abecf4cf542c
draft-paper is a command published in the GitHub repository mizukaizen/hive-doctrine-mcp (0 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 420 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-edit
Edit the mega-plan interactively. Add, remove, or modify features. Usage: /plan-cascade:mega-edit.
hybrid-manual
Load an existing PRD file and enter review mode. Supports JSON format with stories, priorities, dependencies, and acceptance criteria.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.