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/stacklok/toolhive/post-tool-usegit clone --depth 1 https://github.com/stacklok/toolhiveGrade 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 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.
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": "cd \"$CLAUDE_PROJECT_DIR\" && changed_file=\"$CLAUDE_TOOL_ARG_file_path\"; if [ -n \"$changed_file\" ] && echo \"$changed_file\" | grep -q '\\.go$'; then task lint-fix 2>/dev/null; task license-fix 2>/dev/null; fi; exit 0"
}
]
}
]
}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.
- yesterday First seen · 13 lines scan A 97f6a8cc0aea
PostToolUse is a hook published in the GitHub repository stacklok/toolhive (2,056 stars, last pushed today), 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-08-30.
Other hooks, from other repositories
PreToolUse
Runs before the agent uses a tool for Bash, mcp__github__push_files and mcp__github__create_or_update_file tool calls, executing require-review.sh via bash (3 commands). From Nosmoht/talos-mcp-server.
PostToolUse
Runs after a tool call finishes for Edit, Write and MultiEdit tool calls, executing validate.sh. From home-operations/yayamlls.
PostToolUse
Runs after a tool call finishes for Write and Edit tool calls, running an inline shell check. From KyaniteHQ/linctl.
SessionStart
Runs when a session starts, executing peephole.sh. From akashsebastian333/peephole.
UserPromptSubmit
Runs when you submit a prompt, before the agent sees it, running echo '💡 Reminder: TDD workflow - write tests FIRST'. From vishnu2kmohan/mcp-server-langgraph.
PostToolUse
Runs after a tool call finishes for Write, Edit and NotebookEdit tool calls, executing batou-hook.sh. From turenlabs/batou.