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/settings.jsongit 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/hooks/statecrafting/spec-spine/post-tool-use)<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.
<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>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 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 | taiWhat 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.
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 · 13 lines scan B 05fd2a57d5b9
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.
Other hooks, from other repositories
PostToolUse
Runs after a tool call finishes for Write and Edit tool calls, executing format_and_lint.sh. From supabase/supabase.
SessionStart
Runs when a session starts on startup, executing install_pkgs.sh. From supabase/supabase.
SessionStart
Runs when a session starts, executing on-start.js via node. From google-gemini/gemini-cli.
PreToolUse
Runs before the agent uses a tool for Bash tool calls, running an inline shell check. From apache/superset.
PreToolUse
Runs before the agent uses a tool, executing pre-write.sh and pre-bash.sh (2 commands). From anthropics/claude-cookbooks.
PreCompact
Runs before the context is compacted for manual and auto tool calls, executing hook-handler.cjs via node (4 commands). From ruvnet/RuView.