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.
curl -O https://raw.githubusercontent.com/statecrafting/spec-spine/main/.claude/skills/verify/SKILL.mdgit clone --depth 1 https://github.com/statecrafting/spec-spineWrote 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/skills/statecrafting/spec-spine/verify)<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.
<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>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.00040 | $0.01286 |
| Opus 5 | $0.00020 | $0.00643 |
| Sonnet 5 | $0.00008 | $0.00257 |
| Haiku 4.5 | $0.00004 | $0.00129 |
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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 121 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 049). 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
## Verificationsection 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.
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.
- yesterday First seen · 121 lines · 40 tokens per session scan A 512c5b11ce3c
verify is a skill published in the GitHub repository statecrafting/spec-spine (10 stars, last pushed today), licensed Apache-2.0. It adds 40 tokens to every session and 1,286 once invoked, about $0.0002 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-09-07.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.