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/audit)<a href="https://agentmods.dev/commands/mizukaizen/hive-doctrine-mcp/audit"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/audit/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/audit"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/audit.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.00415 |
| Opus 5 | $0.00000 | $0.00208 |
| Sonnet 5 | $0.00000 | $0.00083 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
audit 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
/audit
Run a compliance audit against a specified framework.
Usage
/audit --framework "SOC2|ISO27001|GDPR|PCI-DSS|HIPAA|NIST-CSF" [--scope "<specific controls>"] [--period "<date range>"]
Behaviour
1. Load Framework Controls
Load the control set for the specified framework. If --scope is provided, filter to the specified control areas only.
2. Inventory Existing Controls
Scan the project for evidence of security controls:
- Authentication: Look for auth middleware, session management, MFA configuration
- Authorisation: Look for RBAC/ABAC implementations, permission checks
- Encryption: Check TLS configuration, encryption-at-rest settings, key management
- Logging: Check for audit logging, log retention configuration, log protection
- Access control: Check for least-privilege patterns, service account scoping
- Data handling: Check for PII handling, data classification, retention policies
- Incident response: Check for runbooks, alerting configuration, escalation procedures
- Change management: Check for PR requirements, CI/CD gates, deployment procedures
3. Map Controls to Requirements
Create the control matrix mapping discovered controls to framework requirements. For each requirement:
- Met — Control exists, is documented, and evidence shows it operated during the period
- Partially Met — Control exists but has gaps (not documented, not consistently applied, scope too narrow)
- Not Met — No corresponding control found
4. Generate Gap Analysis
For each unmet or partially met requirement:
- What is missing
- What would be needed to achieve compliance
- Estimated effort to remediate
- Suggested priority based on risk
5. Produce Audit Report
Save to security/audits/[framework]/[date]-report.md using the auditor agent's report format.
Display the executive summary with pass rate and critical gaps.
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 · 51 lines · 0 tokens per session scan A 590017355564
audit 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 415 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
close-review
Month-end close / GL compliance check — invokes accounting-reviewer to produce TM-accounting-{slug}.md with double-entry integrity, ASC 606 revenue-recognition, period-lock, and SOX ITGC gaps.
coding-audit
Medical-coding / revenue-cycle compliance audit. Invokes rcm-reviewer to assess autonomous ICD-10-CM / CPT / HCPCS coding for False Claims Act exposure (upcoding/unbundling), NCCI edits + MUEs, medical necessity (LCD/NCD), modifier discipline, HIPAA minimum-necessary — and force a certified-coder (CPC/CCS) sign-off.
procurement-review
Procurement / source-to-pay compliance check — invokes procurement-reviewer to produce TM-procurement-{slug}.md with three-way match, segregation-of-duties, OFAC-screening, and SOX procurement-controls gaps.
tax-review
Tax-filing compliance check — invokes tax-reviewer to produce TM-tax-{slug}.md with MeF e-file schema, Form 8879, PTIN/Circular 230, and IRC §7216 consent gaps.
full-review
Complete patent application review (claims + specification + formalities in parallel).
review-formalities
Check patent application formalities (abstract, title, drawings per MPEP 608).