agentlens: Command for Claude Code

.claude/commands/bmad-bmm-check-implementation-readiness.md

check-implementation-readiness is a command for Claude Code from agentkitai/agentlens. It costs 39 tokens per session (103 once invoked), scanned A, a copy of check-implementation-readiness, MIT.

A review workflow that checks product requirements, architecture decisions, and planned epics and stories before coding starts. It looks for missing information and disagreements between those documents.

In plain words
What is it for?
Use it to assess whether project plans are complete and consistent enough for development.
Why use it?
It can reveal gaps or misalignment early, before they cause problems during implementation.

Command for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

This is agentkitai/agentlens's own configuration. It tells Claude Code how to work on agentlens itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentlens configures →

Reuse

Borrowing it

Nothing to install: this file belongs to agentkitai/agentlens. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/agentkitai/agentlens/main/.claude/commands/bmad-bmm-check-implementation-readiness.md
Clone the repo
git clone --depth 1 https://github.com/agentkitai/agentlens

Made for: Claude Code.

Wrote 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.

agentmods badge for check-implementation-readiness

README.md
[![agentmods](https://agentmods.dev/badge/commands/agentkitai/agentlens/bmad-bmm-check-implementation-readiness/github.svg)](https://agentmods.dev/commands/agentkitai/agentlens/bmad-bmm-check-implementation-readiness)
Your own site
<a href="https://agentmods.dev/commands/agentkitai/agentlens/bmad-bmm-check-implementation-readiness"><img src="https://agentmods.dev/badge/commands/agentkitai/agentlens/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.

agentmods 80×15 button for check-implementation-readiness

Your own site · 80×15
<a href="https://agentmods.dev/commands/agentkitai/agentlens/bmad-bmm-check-implementation-readiness"><img src="https://agentmods.dev/badge/commands/agentkitai/agentlens/bmad-bmm-check-implementation-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 103 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 84% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00039 $0.00103
Opus 5 $0.00019 $0.00051
Sonnet 5 $0.00008 $0.00021
Haiku 4.5 $0.00004 $0.00010

Measured 9d ago against content hash 41f64c9f81b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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.

Origin

This is a copy

84% identical to check-implementation-readiness — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/bmad-bmm-check-implementation-readiness.md · 8 lines

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!

Changes

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.

  1. 9d ago First seen · 8 lines · 39 tokens per session scan A 41f64c9f81b1

Subscribe to this mod's changes

check-implementation-readiness is a command published in the GitHub repository agentkitai/agentlens (23 stars, last pushed 10d ago), licensed MIT. It adds 39 tokens to every session and 103 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to check-implementation-readiness, differing in 4 lines, and is treated as a copy.