claude-prove: Hook for Claude Code

.claude/settings.json

PreToolUse is a hook for Claude Code from mjmorales/claude-prove. Its token cost is not measured, scanned A, a copy of PostToolUse, MIT.

A set of automatic checks that run before the coding agent uses selected tools. It applies separate checks for searching files, changing files, reading files, and running shell commands.

In plain words
What is it for?
Use it to gate file searches, guard and bound reads or edits, and run state checks before Glob, Grep, Read, Write, Edit, MultiEdit, or Bash calls.
Why use it?
It can enforce search rules, protect the state of ongoing work, and check tool usage before an action changes or examines the project.

Hook for Claude Code

Written for Claude Code: PreToolUse hook event.

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

Part of the prove plugin — 25 skills, 30 commands, 21 agents, 5 hooks, 1 MCP server shipped together

One of 6 entries in settings.json — they are configured in one file and arrive together.

Reuse

Borrowing it

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

Made for: Claude Code.

Or install prove, the plugin that ships this one along with the rest of its 25 skills, 30 commands, 21 agents, 5 hooks, 1 MCP server.

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/mjmorales/claude-prove/pre-tool-use.svg)](https://agentmods.dev/hooks/mjmorales/claude-prove/pre-tool-use)
Your own site
<a href="https://agentmods.dev/hooks/mjmorales/claude-prove/pre-tool-use"><img src="https://agentmods.dev/badge/hooks/mjmorales/claude-prove/pre-tool-use.svg" alt="Measured on agentmods" 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. Scan, not verified.
Origin 89% copy Near-identical to another mod 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 6d 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.

Origin

This is a copy

89% identical to PostToolUse — 19 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/settings.json · 37 lines

What it actually says

{
  "PreToolUse": [
    {
      "matcher": "Glob|Grep",
      "hooks": [
        {
          "type": "command",
          "command": "bun run \"${CLAUDE_PROVE_PLUGIN_DIR:-$HOME/.claude/plugins/prove}/packages/cli/bin/run.ts\" cafi gate",
          "timeout": 10000
        }
      ],
      "_tool": "cafi"
    },
    {
      "matcher": "Write|Edit|MultiEdit",
      "hooks": [
        {
          "type": "command",
          "command": "bun run \"${CLAUDE_PROVE_PLUGIN_DIR:-$HOME/.claude/plugins/prove}/packages/cli/bin/run.ts\" run-state hook guard",
          "timeout": 5000
        }
      ],
      "_tool": "run_state"
    },
    {
      "matcher": "Read|Write|Edit|MultiEdit|Bash",
      "hooks": [
        {
          "type": "command",
          "command": "bun run \"${CLAUDE_PROVE_PLUGIN_DIR:-$HOME/.claude/plugins/prove}/packages/cli/bin/run.ts\" run-state hook bounds",
          "timeout": 5000
        }
      ],
      "_tool": "run_state"
    }
  ]
}
Same file

What else settings.json configures

This page is one entry in a file that holds 6. 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. 6d ago First seen · 37 lines scan A 9fac2e3a74a4

Subscribe to this mod's changes

PreToolUse is a hook published in the GitHub repository mjmorales/claude-prove (2 stars, last pushed 26d ago), 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. It is 89% identical to PostToolUse, differing in 19 lines, and is treated as a copy.