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.
npx agentmods add hooks/future-architect/uzomuzo-oss/post-tool-usegit clone --depth 1 https://github.com/future-architect/uzomuzo-ossWrote 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/future-architect/uzomuzo-oss/post-tool-use)<a href="https://agentmods.dev/hooks/future-architect/uzomuzo-oss/post-tool-use"><img src="https://agentmods.dev/badge/hooks/future-architect/uzomuzo-oss/post-tool-use.svg" alt="Measured on agentmods" 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 4d 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.
What it actually says
{
"PostToolUse": [
{
"matcher": "Edit|Write",
"hooks": [
{
"type": "command",
"command": "if echo \"$CLAUDE_TOOL_INPUT\" | grep -qE '[/\"]\\.github/(instructions/|AGENTS\\.base\\.md\")'; then make -C \"$(git rev-parse --show-toplevel)\" sync-instructions >&2; fi"
}
]
}
]
}What else settings.json configures
This page is one entry in a file that holds 3. 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.
- 4d ago First seen · 13 lines scan A 672dd1f33504
PostToolUse is a hook published in the GitHub repository future-architect/uzomuzo-oss (32 stars, last pushed yesterday), licensed Apache-2.0. 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-09-01.
Other hooks, from other repositories
PostToolUse
Runs after a tool call finishes for Edit, Write, Edit, Write, MultiEdit and Bash tool calls, executing format-and-lint.sh (2 commands). From chainloop-dev/chainloop.
SessionStart
Runs when a session starts, running chainloop trace hook claude session-start. From chainloop-dev/chainloop.
PreToolUse
Runs before the agent uses a tool for AskUserQuestion, Bash, Bash, Glob, Grep, Read, Edit, Write, NotebookEdit, Bash, Edit, Write, MultiEdit, NotebookEdit, Write, Edit, MultiEdit and mcp__filesystem__* tool calls, executing notify.cjs, windows-command-detector.cjs, bash-shell-guard.cjs, git-commit-block.cjs…
PreToolUse
Runs before the agent uses a tool for Bash tool calls, executing commit-gate.sh. From AndrewDryga/emisar.
PreToolUse
Runs before the agent uses a tool for Bash, Task, Write, Edit and Read tool calls, executing bash-guard.ps1, validate-commit.ps1, validate-push.ps1, circuit-guard.sh, pre-code-gate.ps1 and file-history.sh (6 commands). From tranhieutt/software_development_department.
PreToolUse
Runs before the agent uses a tool for Bash, Edit and Write tool calls, executing prevent-main-commit.sh, prevent-main-edit.sh and prevent-generated-edit.sh (5 commands). From hiromaily/docs-ssot.