What is speckit.spex-gates.stamp?

A final verification step for completed work. It checks tests, code cleanliness, compliance with the written specification, and differences between the implementation and that specification.

Use it as the last check in a development pipeline, especially when work follows a written specification. It verifies the work but does not also merge, create a pull request, or clean up.

It helps catch problems before work is declared complete or moved further through the delivery process.

speckit.spex-gates.stamp — Command for Claude Code by rhuss

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.

Clone the repo

git clone --depth 1 https://github.com/rhuss/cc-spex

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/rhuss/cc-spex/speckit.spex-gates.stamp/github.svg)](https://agentmods.dev/commands/rhuss/cc-spex/speckit.spex-gates.stamp)

Your own site

<a href="https://agentmods.dev/commands/rhuss/cc-spex/speckit.spex-gates.stamp"><img src="https://agentmods.dev/badge/commands/rhuss/cc-spex/speckit.spex-gates.stamp/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/rhuss/cc-spex/speckit.spex-gates.stamp"><img src="https://agentmods.dev/badge/commands/rhuss/cc-spex/speckit.spex-gates.stamp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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 441 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 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.1	$0.00019	$0.00441
Opus 5	$0.00010	$0.00220
Sonnet 5	$0.00004	$0.00088
Haiku 4.5	$0.00002	$0.00044

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

Security

Grade A, and why

speckit.spex-gates.stamp 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 10d 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.

specs/038-neutral-command-vocab/pre-rewrite-snapshot/spex-gates/commands/speckit.spex-gates.stamp.md · 49 lines

What it actually says

Stamp - Final Completion Gate

Ship Pipeline Guard

If .specify/.spex-state exists and its status is running, this command is part of an autonomous pipeline. Check the ask field:

If ask is "smart" or "never": suppress all user prompts (do NOT use AskUserQuestion), complete the stamp autonomously, and return immediately so the pipeline can advance.
If ask is "always": prompt the user as normal.

if [ -f ".specify/.spex-state" ]; then
  STATUS=$(jq -r '.status // empty' .specify/.spex-state 2>/dev/null)
  ASK=$(jq -r '.ask // "always"' .specify/.spex-state 2>/dev/null)
  if [ "$STATUS" = "running" ] && [ "$ASK" != "always" ]; then
    echo "AUTONOMOUS_MODE=true"
  else
    echo "AUTONOMOUS_MODE=false"
  fi
else
  echo "AUTONOMOUS_MODE=false"
fi

In autonomous mode: do NOT output a completion summary, do NOT ask "Shall I proceed?", do NOT suggest next steps. Complete the stamp and return.

Relationship to /speckit-spex-finish

/speckit-spex-stamp runs verification only. For verification + merge/PR/cleanup in one step, use /speckit-spex-finish instead.

Purpose

This is the final gate before claiming work is complete. It delegates to the full verification command.

Execution

Invoke speckit.spex-gates.verify with any arguments passed to this command.

The verify command runs all quality gates:

Full test suite
Code hygiene review
Spec compliance validation (100% required)
Spec drift check
Success criteria verification

Only after all gates pass can work be claimed as complete.

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.

10d ago First seen · 49 lines · 19 tokens per session scan A a28faefd39a7

Subscribe to this mod's changes

speckit.spex-gates.stamp is a command published in the GitHub repository rhuss/cc-spex (116 stars, last pushed 21d ago), licensed Apache-2.0. It adds 19 tokens to every session and 441 once invoked, about $0.0001 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-30.

Testing

prototype

You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.

grainulation/grainulator · 0 tokens

verify

Run repository verification using the verification-loop skill.

cloudnative-co/claude-code-starter-kit · 9 tokens

qa-changes

This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…

OpenHands/extensions · 63 tokens

speckit.spex-gates.stamp