clawstash: Hook for Claude Code

.claude/settings.json

PreToolUse is a hook for Claude Code from fo0/clawstash. Its token cost is not measured, scanned A, original, MIT.

A pre-tool safety hook that checks Bash commands before they run, especially commands that create a Git commit.

In plain words
What is it for?
Use it to review staged agent-related files such as CLAUDE.md, AGENTS.md, or documentation before a Git commit.
Why use it?
It warns when configuration or documentation files are staged, helping catch unintended files before committing.

Hook for Claude Code

Written for Claude Code: PreToolUse hook event.

This is fo0/clawstash's own configuration. It tells Claude Code how to work on clawstash 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 clawstash configures →

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

Reuse

Borrowing it

Nothing to install: this file belongs to fo0/clawstash. 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/fo0/clawstash/main/.claude/settings.json
Clone the repo
git clone --depth 1 https://github.com/fo0/clawstash

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 PreToolUse

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

Your own site · 80×15
<a href="https://agentmods.dev/hooks/fo0/clawstash/pre-tool-use"><img src="https://agentmods.dev/badge/hooks/fo0/clawstash/pre-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 A 0 findings. 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 A, and why

PreToolUse 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 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.

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.

.claude/settings.json · 13 lines

What it actually says

{
  "PreToolUse": [
    {
      "matcher": "Edit|Write",
      "hooks": [
        {
          "type": "command",
          "command": "command -v jq >/dev/null 2>&1 || { printf '%s' '{\"hookSpecificOutput\":{\"hookEventName\":\"PreToolUse\",\"additionalContext\":\"Quality-config guard is inert on this machine: jq is not installed, so the hook cannot read the edited path and protects nothing. Install jq, or say so in the report - until then linter/formatter config edits are unguarded.\"}}'; exit 0; }; f=$(jq -r '.tool_input.file_path // empty'); case \"${f##*/}\" in .prettierrc.json|eslint.config.js) printf '%s' '{\"hookSpecificOutput\":{\"hookEventName\":\"PreToolUse\",\"permissionDecision\":\"deny\",\"permissionDecisionReason\":\"Quality-tool config is protected: a red check is fixed in the code, not by weakening the rule that caught it. If editing this config is itself the task, the user applies it or re-gates the path with a permissions.ask entry.\"}}';; esac; exit 0"
        }
      ]
    }
  ]
}
Same file

What else settings.json configures

This page is one entry in a file that holds 4. 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. 1mo ago Changed · -9 lines scan B → A c87f220804bd
  2. 1mo ago Changed · +9 lines ea36c531254d
  3. 2mo ago First seen · 13 lines scan B 2be7f48c3fca

Subscribe to this mod's changes

PreToolUse is a hook published in the GitHub repository fo0/clawstash (1 stars, last pushed today), licensed MIT. Its token cost is not measured: a hook is shell that never enters the context. 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-08-31.