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.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/instructions/statecrafting/spec-spine/claude-md)<a href="https://agentmods.dev/instructions/statecrafting/spec-spine/claude-md"><img src="https://agentmods.dev/badge/instructions/statecrafting/spec-spine/claude-md/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/instructions/statecrafting/spec-spine/claude-md"><img src="https://agentmods.dev/badge/instructions/statecrafting/spec-spine/claude-md.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.02418 | $0.02418 |
| Opus 5 | $0.01209 | $0.01209 |
| Sonnet 5 | $0.00484 | $0.00484 |
| Haiku 4.5 | $0.00242 | $0.00242 |
Grade A, and why
spec-spine CLAUDE.md 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What this is
spec-spine turns a markdown spec corpus into a typed, hash-verifiable authority
ledger and refuses code that drifts from its owning spec at PR time. It is a
three-crate Rust workspace publishing an installable library + CLI, plus npm and
PyPI shims that ship the prebuilt binary. Read docs/design/00-architecture.md
first: it is the load-bearing design doc (crate layout, full Config, public
API, exit codes, schema plan, and the provenance of every ported algorithm).
Commands
The toolchain is pinned in rust-toolchain.toml (channel 1.92.0); MSRV is
1.85 / edition 2024. Always pass --locked; CI does, and the committed
Cargo.lock is part of the determinism contract (tree-sitter grammars are
pinned exact).
cargo build --workspace --locked
cargo test --workspace --locked
cargo clippy --workspace --all-targets --locked -- -D warnings
cargo fmt --all --check
# A single test / one test file:
cargo test -p spec-spine-core --test couple # one integration test file
cargo test -p spec-spine-core compile:: # tests matching a path
cargo test --workspace emitted_registry_conforms # one test by name
# Run the CLI from the checkout (the dogfood gate chain):
cargo run -p spec-spine-cli -- compile # writes .derived/spec-registry/by-spec/<id>.json shards
cargo run -p spec-spine-cli -- index check # staleness gate (exit 2 if stale)
cargo run -p spec-spine-cli -- lint --fail-on-warn
cargo run -p spec-spine-cli -- couple --base origin/main --head HEAD
cargo run -p spec-spine-cli -- index coverage # which source files no spec specifically claims (spec 032)
Exit codes are a stable contract: 0 ok · 1 validation failure / not found /
drift · 2 stale · 3 I/O / parse / schema / config. They are mapped in
exactly one place (crates/spec-spine-cli/src/main.rs via Error::exit_code()).
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 · 163 lines · 2,418 tokens per session scan A 41a92f1bf949
spec-spine CLAUDE.md is an instructions file published in the GitHub repository statecrafting/spec-spine (10 stars, last pushed today), licensed Apache-2.0. It adds 2,418 tokens to every session, about $0.0121 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 instructions, from other repositories
flow-like copilot-instructions.md
Copilot instructions for Rheosoph/flow-like, covering flow-like wasm node development — rust, project overview, build & test, architecture and pin types.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.