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/vinta/hal-9000/post-tool-usegit clone --depth 1 https://github.com/vinta/hal-9000Grade 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 2d 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",
"hooks": [
{
"type": "command",
"command": "bin/hal sync 2>/dev/null || true",
"if": "Edit(/dotfiles/hal_dotfiles.json)",
"timeout": 30,
"statusMessage": "Syncing dotfiles..."
},
{
"type": "command",
"command": "make lint-python >&2 || exit 2",
"if": "Edit(**/*.py)",
"timeout": 30,
"statusMessage": "Linting Python code..."
},
{
"type": "command",
"command": "make lint-ansible >&2 || exit 2",
"if": "Edit(/playbooks/**)",
"timeout": 30,
"statusMessage": "Linting Ansible playbooks..."
}
]
},
{
"matcher": "Write",
"hooks": [
{
"type": "command",
"command": "make lint-python >&2 || exit 2",
"if": "Write(**/*.py)",
"timeout": 30,
"statusMessage": "Linting Python code..."
},
{
"type": "command",
"command": "make lint-ansible >&2 || exit 2",
"if": "Write(/playbooks/**)",
"timeout": 30,
"statusMessage": "Linting Ansible playbooks..."
}
]
}
]
}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.
- 2d ago First seen · 49 lines scan A 018700184458
PostToolUse is a hook published in the GitHub repository vinta/hal-9000 (125 stars, last pushed 5d ago), 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 Edit, Write and MultiEdit tool calls, running an inline shell check. From telepresenceio/telepresence.
PostToolUse
Runs after a tool call finishes for Edit, Write and MultiEdit tool calls, running an inline shell check. From telepresenceio/telepresence.
PostToolUse
Runs after a tool call finishes for Edit(**src/**), Write(**src/**), Edit(**tests/**), Write(**tests/**), Bash(**git commit**), Bash(**git pull**), Bash(**git checkout**) and Bash(**git merge**) tool calls, executing update-context-files.py via python with --diff, --quiet, --fix, --recent-work, --show-current…
SessionStart
Runs when a session starts, running an inline shell check (3 commands). From vishnu2kmohan/mcp-server-langgraph.
PreToolUse
Runs before the agent uses a tool for Bash(**git commit**) tool calls, executing validate_mintlify_docs.py via python3 with --check and --strict (2 commands). From vishnu2kmohan/mcp-server-langgraph.
SessionEnd
Runs when a session ends, running echo '📊 Session complete. Remember: /clear before switching. From vishnu2kmohan/mcp-server-langgraph.