spec-spine: Skill for Claude Code

.claude/skills/verify/SKILL.md

verify is a skill for Claude Code from statecrafting/spec-spine. It costs 40 tokens per session (1,314 once invoked), scanned A, original, Apache-2.0.

A routine that runs the acceptance commands written for one project specification. Acceptance commands are the checks that show whether a requested change meets its stated requirements.

In plain words
What is it for?
It is for running a specification’s verification commands in order, previewing the plan first, and reporting which acceptance requirements each command checks.
Why use it?
It rehearses the same verification stage used after a change is merged, while reporting failures honestly and warning when uncommitted files could affect the result.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions AGENTS.md.

This is statecrafting/spec-spine's own configuration. It tells Claude Code how to work on spec-spine 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 spec-spine configures →

Reuse

Borrowing it

Nothing to install: this file belongs to statecrafting/spec-spine. 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/statecrafting/spec-spine/main/.claude/skills/verify/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/statecrafting/spec-spine

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 verify

README.md
[![agentmods](https://agentmods.dev/badge/skills/statecrafting/spec-spine/verify/github.svg)](https://agentmods.dev/skills/statecrafting/spec-spine/verify)
Your own site
<a href="https://agentmods.dev/skills/statecrafting/spec-spine/verify"><img src="https://agentmods.dev/badge/skills/statecrafting/spec-spine/verify/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 verify

Your own site · 80×15
<a href="https://agentmods.dev/skills/statecrafting/spec-spine/verify"><img src="https://agentmods.dev/badge/skills/statecrafting/spec-spine/verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,314 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.01314
Opus 5.5 $0.00016 $0.00526
Sonnet 5.5 $0.00008 $0.00263
Haiku 4.5 $0.00004 $0.00131

Measured 1mo ago against content hash f5f8fcb804f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

verify 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 1mo 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.

.claude/skills/verify/SKILL.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/verify : the spec's Verification block, locally

Runs the ## Verification section of specs/<id>/spec.md exactly the way an orchestrator's verify stage will run it after merge: every non-comment line inside a ```verify:cli fence, from the repository root, in order, stopping at the first non-zero exit. This is the local rehearsal of the "Satisfy the spec's acceptance criteria verbatim" step of AGENTS.md, "Working the backlog".

The verb is spec-spine verify (spec 043). It requires spec-spine 0.15.0 or later.

Step 0: scope

  • The argument is the spec id. The verb accepts the short form (049) as well as the full one. Without an argument, stop and ask; do not guess from the branch name.
  • git status --porcelain: the post-merge run happens in a clean checkout of the merged sha, so a pass that depends on an uncommitted file is not a pass. Warn when the tree is dirty and say which files.
  • Read the spec's acceptance criteria and its ## Verification section once, so the report can say which criterion each command exercises.

Step 1: read the plan before running it

spec-spine verify <spec-id> --plan

--plan prints the commands, one per line, and runs none of them. This is the safety affordance for the one verb that executes what the corpus declares, and it is how you read a ## Verification block someone else wrote. Read it before Step 2 whenever the spec is not one this session authored.

Step 2: run

spec-spine verify <spec-id>

Use the binary invocation AGENTS.md names. Outcomes, as the verb words them:

outcome exit meaning
passed 0 at least one command ran; all exited 0
not-declared 0 nothing to run; an honest zero, not a pass
failed 1 a command exited non-zero; later commands did not run
no such spec 1 the id resolves to no spec

A failing command's own exit code is reported in the payload (failure.exitCode under --json), not as the process's exit code: the process stays inside the documented 0/1/2/3 contract. Do not report the payload code as the verb's code, or the reverse.

Read the full file on GitHub · 122 lines

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. 1mo ago Changed · +1 lines f5f8fcb804f0
  2. 1mo ago Changed a4f93afdb954
  3. 2mo ago First seen · 121 lines · 40 tokens per session scan A 512c5b11ce3c

Subscribe to this mod's changes

verify is a skill published in the GitHub repository statecrafting/spec-spine (11 stars, last pushed 8d ago), licensed Apache-2.0. It adds 40 tokens to every session and 1,314 once invoked, about $0.0002 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-07.

Related

verify compared with skills from other repositories

verify next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
verifystatecrafting/spec-spineSkill118d agoApache-2.0A40Claude Code
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code