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.
npx skills add mizukaizen/hive-doctrine-mcp --skill deliverable-reviewgit 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/skills/mizukaizen/hive-doctrine-mcp/deliverable-review)<a href="https://agentmods.dev/skills/mizukaizen/hive-doctrine-mcp/deliverable-review"><img src="https://agentmods.dev/badge/skills/mizukaizen/hive-doctrine-mcp/deliverable-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/skills/mizukaizen/hive-doctrine-mcp/deliverable-review"><img src="https://agentmods.dev/badge/skills/mizukaizen/hive-doctrine-mcp/deliverable-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.00567 |
| Opus 5 | $0.00000 | $0.00283 |
| Sonnet 5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
deliverable-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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Deliverable Review
Use when reviewing a deliverable before handing it off to the client. Checks quality, completeness, presentation, and readiness for client consumption.
Trigger
Invoke this skill when a feature or milestone is complete and ready for client review. Run this before every client-facing delivery.
Review Checklist
1. Acceptance Criteria
- Read the original spec or user story
- Verify each acceptance criterion is met
- Flag any criteria that were modified during implementation (and ensure the client approved the change)
2. Functional Quality
- Run the full test suite — all tests must pass
- Test the happy path manually
- Test at least 2 edge cases per feature
- Verify error states show user-friendly messages (not stack traces or raw error codes)
- Check loading states and empty states
3. Visual Quality
- Compare implementation against design mockups (if provided)
- Check responsive behaviour at 375px, 768px, and 1440px widths
- Verify consistent spacing, typography, and colour usage
- Check dark mode if applicable
4. Code Quality
- No debug statements (console.log, print, debugger)
- No commented-out code
- No hardcoded values that should be configuration
- No TODO comments without associated tracked issues
- Dependencies are up to date and free of known vulnerabilities
5. Documentation
- README includes setup and run instructions
- API endpoints are documented (if applicable)
- Environment variables are listed in
.env.example - Any complex business logic has inline comments explaining "why"
6. Presentation
- Demo script prepared (step-by-step walkthrough for the client)
- Known limitations documented honestly
- Next steps clearly outlined
Output
Generate a review report at clients/[client-slug]/docs/reviews/review-[YYYY-MM-DD].md:
# Deliverable Review: [Feature/Milestone]
**Date:** [YYYY-MM-DD]
**Reviewer:** [Name]
## Verdict: Ready / Needs Work / Blocked
## Acceptance Criteria: [X/Y] met
## Issues Found
| # | Severity | Description | Status |
|---|----------|-------------|--------|
| 1 | High | [Issue] | Open |
## Recommendation
[Ship as-is / Fix issues first / Needs rework]
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.
- 12d ago First seen · 74 lines · 0 tokens per session scan A 1ee4fbd287a1
deliverable-review is a skill 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 567 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 skills, from other repositories
java-best-practices
Java coding best practices. Use when writing or reviewing Java code (17+). Covers modern features, error handling, and patterns.
code-simplifier
Post-session code review and cleanup against a working tree of changes. Analyzes git diff to simplify, consolidate, and align changed code with the existing codebase — modernize syntax, remove unnecessary complexity, consolidate duplicated logic, catch efficiency issues. Use after a substantive working session, or…
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
link-check
Verify @file references in AIWG skills and agents against the linking contract — per-file or corpus-wide, with optional auto-fix.
thermo-nuclear-code-quality-review
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.