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/gmickel/flow-nextWrote 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/gmickel/flow-next/spec-completion-review)<a href="https://agentmods.dev/commands/gmickel/flow-next/spec-completion-review"><img src="https://agentmods.dev/badge/commands/gmickel/flow-next/spec-completion-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/commands/gmickel/flow-next/spec-completion-review"><img src="https://agentmods.dev/badge/commands/gmickel/flow-next/spec-completion-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.00013 | $0.00116 |
| Opus 5.5 | $0.00005 | $0.00046 |
| Sonnet 5.5 | $0.00003 | $0.00023 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
spec-completion-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 20d 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
IMPORTANT: This command MUST invoke the skill flow-next-spec-completion-review
The ONLY purpose of this command is to call the flow-next-spec-completion-review skill. You MUST use that skill now.
Arguments: $ARGUMENTS
Pass the arguments to the skill. The skill handles the review logic.
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.
- 20d ago Changed af064dbf52dc
- 29d ago Changed · +1 lines 394b25a14471
- 1mo ago First seen · 14 lines · 13 tokens per session scan A 0da3c4e174a6
spec-completion-review is a command published in the GitHub repository gmickel/flow-next (713 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 116 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other commands, from other repositories
refactor
Refactor and optimize [code].
battery
The full independent-verification battery for a finished branch: a fresh-context acceptance verifier that RE-EXECUTES the verification commands against a stated baseline, a multi-lens review, and the kit:advisor extra lens, dispatched in parallel at prescribed model tiers, findings merged into one verdict, fixes…
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
check-pr
Check a PR's CI status, reviews, comments, and merge readiness.
speckit.plan
Execute the implementation planning workflow using the plan template to generate design artifacts.