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/post-tool-use)<a href="https://agentmods.dev/hooks/gaia-react/gaia/post-tool-use"><img src="https://agentmods.dev/badge/hooks/gaia-react/gaia/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/gaia-react/gaia/post-tool-use"><img src="https://agentmods.dev/badge/hooks/gaia-react/gaia/post-tool-use.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
PostToolUse 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"PostToolUse": [
{
"matcher": "AskUserQuestion",
"hooks": [
{
"type": "command",
"command": "\"$(git rev-parse --show-toplevel 2>/dev/null || printf %s \"${CLAUDE_PROJECT_DIR:-.}\")/.claude/hooks/audit-loop-ask-grant.sh\"",
"timeout": 15,
"statusMessage": "Recording audit checkpoint answer…"
}
]
},
{
"matcher": "EnterWorktree",
"hooks": [
{
"type": "command",
"command": "\"$(git rev-parse --show-toplevel 2>/dev/null || printf %s \"${CLAUDE_PROJECT_DIR:-.}\")/.claude/hooks/provision-worktree.sh\""
},
{
"type": "command",
"command": "\"$(git rev-parse --show-toplevel 2>/dev/null || printf %s \"${CLAUDE_PROJECT_DIR:-.}\")/.claude/hooks/workflow-doctrine-inject.sh\""
}
]
},
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"if": "Bash(gh pr merge *)",
"command": "\"$(git rev-parse --show-toplevel 2>/dev/null || printf %s \"${CLAUDE_PROJECT_DIR:-.}\")/.claude/hooks/pr-merge-cost.sh\""
},
{
"type": "command",
"command": "\"$(git rev-parse --show-toplevel 2>/dev/null || printf %s \"${CLAUDE_PROJECT_DIR:-.}\")/.claude/hooks/capture-red-observations.sh\""
},
{
"type": "command",
"if": "Bash(gh *)",
"command": "\"$(git rev-parse --show-toplevel 2>/dev/null || printf %s \"${CLAUDE_PROJECT_DIR:-.}\")/.claude/hooks/debt-sentinel-touch.sh\""
},
{
"type": "command",
"if": "Bash(gh pr merge *)",
"command": "\"$(git rev-parse --show-toplevel 2>/dev/null || printf %s \"${CLAUDE_PROJECT_DIR:-.}\")/.claude/hooks/issue-claim-release.sh\""
},
{
"type": "command",
"if": "Bash(gh pr create *)",
"command": "\"$(git rev-parse --show-toplevel 2>/dev/null || printf %s \"${CLAUDE_PROJECTWhat 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.
- 3d ago Changed · +14 lines 6cf37b8286fc
- 8d ago Changed · -5 lines e13bbd7a784f
- 9d ago Changed · +11 lines 90891f74ad3e
- 15d ago Changed · +11 lines 29495f9439cf
- 16d ago Changed · -4 lines 3005104867ff
- 17d ago Changed · +8 lines fa4ab9ace5a8
- 1mo ago Changed bf47a60743e7
- 1mo ago First seen · 46 lines scan A 612a19122f5b
PostToolUse 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 A with 0 findings. 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, executing guard-no-verify.sh. From kopp0510/claude-dd.
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.