Borrowing it
Nothing to install: this file belongs to Alberto-Codes/docvet. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Alberto-Codes/docvet/main/.claude/commands/bmad-bmm-check-implementation-readiness.mdgit clone --depth 1 https://github.com/Alberto-Codes/docvetWrote 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/alberto-codes/docvet/bmad-bmm-check-implementation-readiness)<a href="https://agentmods.dev/commands/alberto-codes/docvet/bmad-bmm-check-implementation-readiness"><img src="https://agentmods.dev/badge/commands/alberto-codes/docvet/bmad-bmm-check-implementation-readiness/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/alberto-codes/docvet/bmad-bmm-check-implementation-readiness"><img src="https://agentmods.dev/badge/commands/alberto-codes/docvet/bmad-bmm-check-implementation-readiness.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.00031 | $0.00088 |
| Opus 5 | $0.00015 | $0.00044 |
| Sonnet 5 | $0.00006 | $0.00018 |
| Haiku 4.5 | $0.00003 | $0.00009 |
Grade A, and why
check-implementation-readiness 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
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md, READ its entire contents and follow its directions exactly!
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 · 7 lines · 31 tokens per session scan A c9589d2a0445
check-implementation-readiness is a command published in the GitHub repository Alberto-Codes/docvet (9 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 88 once invoked, about $0.0002 per session on Opus 5. 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
mdlinter
Check or fix markdown linting issues with optional scope.
generate
Generate documentation for specific feature or component.
n1-analyze
Analyze codebase for N+1 queries and performance issues using parallel agents.
audit
Audit documentation quality and coverage.
plan
Generate documentation plan for project or feature.
tdd-bug
Fix a bug with regression test first.