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/next/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/next)<a href="https://agentmods.dev/skills/statecrafting/spec-spine/next"><img src="https://agentmods.dev/badge/skills/statecrafting/spec-spine/next/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/next"><img src="https://agentmods.dev/badge/skills/statecrafting/spec-spine/next.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.00820 |
| Opus 5.5 | $0.00016 | $0.00328 |
| Sonnet 5.5 | $0.00008 | $0.00164 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
next 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/next: the next work order
The backlog is the spec corpus. Step 1 of AGENTS.md "Working the
backlog" picks the spec, and this skill computes that pick from typed
reads. Two rules sit on top of what the tool reports:
- Approval is a human act.
spec-spine registry plan(spec 035) schedules byimplementationanddepends_on; it will offer astatus: draftspec whose dependencies are met. A draft is never a work order: drop it from the ready set and list it as "awaiting approval". - One session, one spec. A spec at
implementation: in-progressis in flight (spec 041): it belongs to another session or to an interrupted one. Report it separately; never offer it as new work unless a human names it.
Step 1: the ready set, typed
spec-spine registry plan --json
Exit 0 prints {"ready": [...ids in dependency order...], "blocked": [{"id", "blockedBy": [{"id", "state"}]}]}.
A non-zero exit is a halt: V-014 names a dependency cycle (schedule
nothing from a broken graph; print the diagnostic verbatim), and any
other failure means the registry is unreadable (/setup, or a stale
binary).
Parsing this output is a typed read (AGENTS.md "Governed artifact reads").
Reading .statecraft/derived/ is not.
Step 2: apply the two rules
For each ready id, read its record:
spec-spine registry show <id> --json
statusis notapproved: move it to "awaiting approval".implementationisin-progress: move it to "in flight".- Otherwise it is a work order. Keep the tool's order.
Record specs (the bootstrap, a thesis, a harness spec at n-a or
complete) never appear in ready; if one does, its implementation
is wrong and that is a finding, not a pick.
Step 3: the pick, cross-checked
Take the first work order unless a human named another. Read its
## Territory (or equivalent) for an operator prerequisite (a service, a
credential, a sibling repository) that is missing: that is a stop at
step 1 of the protocol, reported exactly, not mocked around.
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.
- 1mo ago Changed 0e63877f972f
- 1mo ago Changed e233f5ff8a91
- 2mo ago First seen · 90 lines · 40 tokens per session scan A 6bd284099b2e
next 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 820 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.
next compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| nextstatecrafting/spec-spine | Skill | 11 | 8d ago | Apache-2.0 | A | 40 | Claude Code |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |