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/setup/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/setup)<a href="https://agentmods.dev/skills/statecrafting/spec-spine/setup"><img src="https://agentmods.dev/badge/skills/statecrafting/spec-spine/setup.svg" alt="Measured on agentmods" 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.00045 | $0.01007 |
| Opus 5 | $0.00023 | $0.00504 |
| Sonnet 5 | $0.00009 | $0.00201 |
| Haiku 4.5 | $0.00005 | $0.00101 |
Grade A, and why
setup 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/setup
Get a fresh clone operational. After this completes, /init can report
lifecycle and structural counts through spec-spine, never by ad-hoc
parsing of .derived/**/*.json (.claude/rules/governed-artifact-reads.md).
Process
1. Install the pinned spec-spine
AGENTS.md pins the version and names the invocation (a binary on PATH,
a package wrapper, or an in-tree build). CI runs the pinned one, so a local
pass on another version proves nothing: a different version is a halt.
Any one route:
cargo install spec-spine-cli --version <pin> --locked # with a Rust toolchain
npm i -g spec-spine@<pin> # prebuilt binary, no toolchain
uvx spec-spine@<pin> --version # Python, ephemeral
Verify: spec-spine --version prints the pin. When AGENTS.md says the
binary is built from this checkout, build it as it says instead and use
that path for every command below.
2. Stack toolchain
Install whatever AGENTS.md (or CLAUDE.md) names for the language
gates: a pinned toolchain file, a package manager, optional linters. Report
each as present or absent; a missing optional tool is a note, a missing
required one is a halt. jq is a convenience the hooks in
.claude/settings.json use; each hook says what it skipped when jq is
absent.
3. Fetch the base ref
The coupling gate diffs against the default branch on the remote:
git fetch origin main
4. Verify the governed loop
Run the gate exactly as AGENTS.md "Working the backlog" lists it under
"Run the gate before every commit". The governance floor is:
spec-spine compile
spec-spine index
spec-spine lint --fail-on-warn
spec-spine index check
spec-spine couple --base origin/main --head HEAD
spec-spine index coverage --fail-on-untraced # when [coupling] require_ownership is on
then the stack's own build, tests, and lints. On a clean checkout
compile and index are deterministic no-ops; if
git status --short -- .derived/ shows a diff afterwards, the committed
shards were stale. Say so and leave the diff for the session to commit
(chore(derived): ...); do not hide it. Halt on the first failing step
and surface its output verbatim.
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 · 115 lines · 45 tokens per session scan A 5d9139e52e00
setup is a skill published in the GitHub repository statecrafting/spec-spine (10 stars, last pushed today), licensed Apache-2.0. It adds 45 tokens to every session and 1,007 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
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.