What is spec-complete?

A command that runs the final steps after a planned feature is implemented: user acceptance testing, documentation, release notes, and a development retrospective.

Use it to verify a completed specification, create user and technical documents, prepare release information, and record lessons learned.

It gathers the checks and project follow-up work needed before release in one process, stopping if acceptance testing rejects the result.

spec-complete — Command by Habib0x0

Install

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.

agentmods

npx agentmods add commands/habib0x0/spec-driven-plugin/spec-complete

Clone the repo

git clone --depth 1 https://github.com/Habib0x0/spec-driven-plugin

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 384 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found 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.

Model	Per session	Once invoked
Fable 5	$0.00019	$0.00384
Opus 5	$0.00010	$0.00192
Sonnet 5	$0.00004	$0.00077
Haiku 4.5	$0.00002	$0.00038

Measured 2d ago against content hash bb636fc4ff86, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

spec-complete 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 2d 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.

commands/spec-complete.md · 46 lines

What it actually says