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/status)<a href="https://agentmods.dev/commands/mizukaizen/hive-doctrine-mcp/status"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/status/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/status"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/status.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.00430 |
| Opus 5 | $0.00000 | $0.00215 |
| Sonnet 5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
status 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 9d 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: /status
Generate a cross-project status report for all active client projects.
Usage
/status
Process
Step 1: Discover Active Projects
Scan clients/ directory for all project folders. Read each project's STATUS.md and SCOPE.md.
Step 2: Generate Dashboard
# Agency Status Dashboard
**Generated:** [YYYY-MM-DD HH:MM]
## Active Projects
| Client | Phase | Health | Deadline | Hours Used/Budget | Blockers |
|--------|-------|--------|----------|-------------------|----------|
| [Name] | Build | Green | Apr 15 | 40/120h | None |
| [Name] | QA | Amber | Mar 30 | 95/100h | API docs |
## Attention Required
[List any project where:]
- Hours exceed 80% of budget
- Deadline is within 5 business days
- There are unresolved blockers
- Status has not been updated in 7+ days
## This Week's Deliverables
- [Client A]: [Deliverable] — due [date]
- [Client B]: [Deliverable] — due [date]
## Team Allocation
| Team Member | Current Project | Utilisation |
|-------------|-----------------|-------------|
| [Name] | [Client] | 80% |
Step 3: Health Assessment
Assign health status per project:
- Green: On track, within budget, no blockers
- Amber: Minor risk — timeline pressure, approaching budget limit, or minor blockers
- Red: At risk — over budget, past deadline, or critical blockers
Step 4: Save Report
Save to reports/status-[YYYY-MM-DD].md.
Rules
- Report only facts. Do not speculate about why things are behind.
- If a project's STATUS.md has not been updated in 7+ days, flag it as stale data.
- Include time tracking variance if available (estimated vs actual hours).
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.
- 9d ago First seen · 60 lines · 0 tokens per session scan A 2ac346d4533c
status 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 430 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-status
Show detailed status of mega-plan execution including feature progress and story completion. Usage: /plan-cascade:mega-status.
hybrid-status
Show execution status of all stories in the PRD. Displays batch progress, individual story states, completion percentage, and recent activity logs.
hybrid-complete
Complete Hybrid Ralph task in worktree, verify all stories complete, commit code changes (excluding planning files), merge to target branch, and cleanup worktree directory. Can be run from any directory.
status
Show execution status of all stories in the PRD. Displays batch progress, individual story states, completion percentage, and recent activity logs.
tracker
Append a new S.N entry to audric-build-tracker.md for the work just shipped.
talent-motivation
Build a per-person motivation map from observed behavior using Self-Determination Theory + dopamine-anticipation analysis. Output is a motivation hypothesis plus 1-2 leverage interventions, never a personality profile. Refuses engagement-survey-as-data; refuses generic "you should be more motivating." Sub-system 5 of…