PreToolUse

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

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add hooks/fo0/clawstash/pre-tool-use
Clone the repo
git clone --depth 1 https://github.com/fo0/clawstash

Made for: Claude Code.

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. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade B, and why

PreToolUse 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": "cmd=$(jq -r '.tool_input.command // empty'); if echo \"$cmd\" | grep -qE 'git commit'; then cd \"$CLAUDE_PROJECT_DIR\" || exit 0; staged=$(git diff --cached --name-only 2>/dev/null | grep -E '^(\\.claude/|CLA
.claude/settings.json · 13 lines

What it actually says

{
  "PreToolUse": [
    {
      "matcher": "Bash",
      "hooks": [
        {
          "type": "command",
          "command": "cmd=$(jq -r '.tool_input.command // empty'); if echo \"$cmd\" | grep -qE 'git commit'; then cd \"$CLAUDE_PROJECT_DIR\" || exit 0; staged=$(git diff --cached --name-only 2>/dev/null | grep -E '^(\\.claude/|CLAUDE\\.md|AGENTS\\.md|agent_docs/|docs/wiki/)' || true); [ -n \"$staged\" ] && jq -nc --arg s \"$staged\" '{hookSpecificOutput:{hookEventName:\"PreToolUse\",additionalContext:(\"GitNexus read-only guard: agent-config/doc files are staged -- confirm these are intended (not GitNexus side-effects) before committing, else git restore --staged / git checkout -- :\\n\" + $s)}}'; fi; exit 0"
        }
      ]
    }
  ]
}
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 2be7f48c3fca

Subscribe to this mod's changes

PreToolUse is a hook published in the GitHub repository fo0/clawstash (1 stars, last pushed yesterday), licensed MIT. 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-08-31.