Borrowing it
Nothing to install: this file belongs to gaia-react/gaia. 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/gaia-react/gaia/main/.claude/settings.jsongit clone --depth 1 https://github.com/gaia-react/gaiaWrote 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/gaia-react/gaia/pre-tool-use)<a href="https://agentmods.dev/hooks/gaia-react/gaia/pre-tool-use"><img src="https://agentmods.dev/badge/hooks/gaia-react/gaia/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.
<a href="https://agentmods.dev/hooks/gaia-react/gaia/pre-tool-use"><img src="https://agentmods.dev/badge/hooks/gaia-react/gaia/pre-tool-use.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 8d 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
"statusMessage": "Checking rm -rf safety…" Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"PreToolUse": [
{
"matcher": "Edit|Write|MultiEdit",
"hooks": [
{
"type": "command",
"command": "\"$(git rev-parse --show-toplevel 2>/dev/null || printf %s \"${CLAUDE_PROJECT_DIR:-.}\")/.claude/hooks/block-eslint-config-edit.sh\""
},
{
"type": "command",
"command": "\"$(git rev-parse --show-toplevel 2>/dev/null || printf %s \"${CLAUDE_PROJECT_DIR:-.}\")/.claude/hooks/block-secrets-write.sh\""
},
{
"type": "command",
"command": "\"$(git rev-parse --show-toplevel 2>/dev/null || printf %s \"${CLAUDE_PROJECT_DIR:-.}\")/.claude/hooks/block-manifest-write.sh\""
},
{
"type": "command",
"command": "\"$(git rev-parse --show-toplevel 2>/dev/null || printf %s \"${CLAUDE_PROJECT_DIR:-.}\")/.claude/hooks/block-worktree-path-mismatch.sh\""
},
{
"type": "command",
"command": "\"$(git rev-parse --show-toplevel 2>/dev/null || printf %s \"${CLAUDE_PROJECT_DIR:-.}\")/.claude/hooks/block-audit-loop-write.sh\""
}
]
},
{
"matcher": "Bash|Monitor",
"hooks": [
{
"type": "command",
"command": "\"$(git rev-parse --show-toplevel 2>/dev/null || printf %s \"${CLAUDE_PROJECT_DIR:-.}\")/.claude/hooks/block-handrolled-pr-poll.sh\""
},
{
"type": "command",
"command": "\"$(git rev-parse --show-toplevel 2>/dev/null || printf %s \"${CLAUDE_PROJECT_DIR:-.}\")/.claude/hooks/block-main-destructive-git.sh\"",
"statusMessage": "Checking main-branch protection…"
},
{
"type": "command",
"command": "\"$(git rev-parse --show-toplevel 2>/dev/null || printf %s \"${CLAUDE_PROJECT_DIR:-.}\")/.claude/hooks/block-no-verify.sh\"",
"statusMessage": "Checking commit-floor bypass…"
},
{
"type": "command",
"command": "\"$(git rev-parse --show-topWhat else settings.json configures
This page is one entry in a file that holds 7. 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.
- 8d ago Changed · -1 lines 758e96cbf7ba
- 9d ago Changed · -16 lines 60eaeaef685a
- 10d ago Changed · +5 lines d1182acd5134
- 16d ago Changed · +15 lines scan C → B 6d60da02df05
- 20d ago Changed · -25 lines 840b6a252a1b
- 22d ago Changed · -28 lines 2c29b6cfb217
- 23d ago Changed · -35 lines 39b73b5cdbe5
- 24d ago Changed · -5 lines c54faf85e490
- 25d ago Changed · -4 lines 73d4cc3d1c10
- 26d ago First seen · 233 lines scan C eed40787f82e
PreToolUse is a hook published in the GitHub repository gaia-react/gaia (23 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 B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other hooks, from other repositories
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.
PostToolUse
Runs after a tool call finishes for Bash tool calls, executing hooks.sh via sh (3 commands). From anthropics/claude-plugins-official.
PreCompact
Runs before the context is compacted for manual and auto tool calls, executing hook-handler.cjs via node (4 commands). From ruvnet/RuView.
SessionStart
Runs when a session starts on startup, executing worktree-setup.mjs via bash with --show-toplevel. From openclaw/openclaw.
SessionStart
Runs when a session starts, executing hook-handler.cjs and auto-memory-hook.mjs via node (2 commands). From ruvnet/RuView.