spec-spine: Hook for Claude Code

.claude/settings.json

PostToolUse is a hook for Claude Code from statecrafting/spec-spine. Its token cost is not measured, scanned B, original, Apache-2.0.

An automatic check that runs after editing or writing a file and uses a shell command to detect stale generated data in a spec-spine repository.

In plain words
What is it for?
Use it after file changes in repositories containing a specs directory to check the spec-spine compiled state.
Why use it?
It can reveal when committed derived files no longer match the source specifications after an edit.

Hook for Claude Code

Written for Claude Code: PostToolUse hook event. Also seen: mentions CLAUDE.md; positional $N argument; 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 →

One of 5 entries in settings.json upstream. Installing this one merges just its entry into your config; the other 4 are separate, each on its own page.

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/settings.json
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 PostToolUse

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

Your own site · 80×15
<a href="https://agentmods.dev/hooks/statecrafting/spec-spine/post-tool-use"><img src="https://agentmods.dev/badge/hooks/statecrafting/spec-spine/post-tool-use.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade B, and why

PostToolUse scanned grade B with 1 finding 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 commands this hook runs, not an audit. A hook is shell that executes on your machine at the event it names, which is why every command in it is printed with what was found.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

"command": "command -v jq >/dev/null 2>&1 || { echo '[hook] jq missing, staleness check skipped'; exit 0; }\nfp=$(jq -r '.tool_input.file_path // empty' 2>/dev/null)\n[ -n \"$fp\" ] || exit 0\n# The repo containing the e
.claude/settings.json · 13 lines

How it starts

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

{
  "PostToolUse": [
    {
      "matcher": "Edit|Write",
      "hooks": [
        {
          "type": "command",
          "command": "command -v jq >/dev/null 2>&1 || { echo '[hook] jq missing, staleness check skipped'; exit 0; }\nfp=$(jq -r '.tool_input.file_path // empty' 2>/dev/null)\n[ -n \"$fp\" ] || exit 0\n# The repo containing the edited file, not the session's project: an edit in a\n# sibling checkout must not recompile this one.\nroot=$(git -C \"$(dirname \"$fp\")\" rev-parse --show-toplevel 2>/dev/null) || exit 0\n[ -d \"$root/specs\" ] || exit 0\n# Resolve the spec-spine binary for the repository this hook acts on:\n# $SPEC_SPINE_BIN, then that repository's own release build, then PATH. A repo\n# that builds its own binary must be governed by the one it builds; the PATH\n# fallback keeps an adopter on the published CLI working (spec 051).\nspec_spine_bin() {\n  if [ -n \"${SPEC_SPINE_BIN:-}\" ] && [ -x \"${SPEC_SPINE_BIN}\" ]; then echo \"${SPEC_SPINE_BIN}\"; return 0; fi\n  if [ -x \"$1/target/release/spec-spine\" ]; then echo \"$1/target/release/spec-spine\"; return 0; fi\n  command -v spec-spine 2>/dev/null\n}\nsc=$(spec_spine_bin \"$root\") || sc=''\n[ -n \"$sc\" ] || { echo '[hook] spec-spine absent, staleness check skipped (run /setup)'; exit 0; }\ncase \"$fp\" in\n  */specs/*/spec.md)\n    # The one sanctioned write in these hooks: the session is live and can\n    # commit the recompiled shards with the spec edit that made them stale.\n    \"$sc\" --repo \"$root\" compile >/dev/null 2>&1 \\\n      && echo '[spec-registry] recompiled after spec edit' \\\n      || echo '[spec-registry] compile FAILED after spec edit, run spec-spine compile' ;;\nesac\ncase \"$fp\" in\n  */specs/*/spec.md|*/spec-spine.toml|*/.claude/settings.json|*/.mcp.json|*/.claude/agents/*.md|*/.claude/rules/*.md|*/.claude/skills/*/*.md|*/.github/workflows/*.yml|*/standards/*|*/AGENTS.md|*/CLAUDE.md|*/Makefile|*/docs/design/*)\n    \"$sc\" --repo \"$root\" index check 2>&1 | tai

Read the full file on GitHub · 13 lines

Same file

What else settings.json configures

This page is one entry in a file that holds 5. Installing the file brings all of them; each is measured and scanned on its own page.

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. yesterday First seen · 13 lines scan B 05fd2a57d5b9

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository statecrafting/spec-spine (10 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: a hook is shell that never enters the context. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.