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/withkynam/vibecode-pro-max-kit/post-tool-usegit clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kitGrade 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.
This is a copy
47% identical to SessionStart — 30 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"PostToolUse": [
{
"matcher": "Edit|Write|MultiEdit",
"hooks": [
{
"type": "command",
"command": "node \"$CLAUDE_PROJECT_DIR\"/.claude/hooks/session-state.cjs"
},
{
"type": "command",
"command": "node \"$CLAUDE_PROJECT_DIR\"/.claude/hooks/post-edit-simplify-reminder.cjs"
}
]
},
{
"matcher": "Write",
"hooks": [
{
"type": "command",
"command": "node \"$CLAUDE_PROJECT_DIR\"/.claude/hooks/post-write-plan-check.mjs"
}
]
},
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "node \"$CLAUDE_PROJECT_DIR\"/.claude/hooks/post-commit-lint.mjs"
}
]
}
]
}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 · 35 lines scan A f4765cad4f49
PostToolUse is a hook published in the GitHub repository withkynam/vibecode-pro-max-kit (1,105 stars, last pushed 2mo 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. It is 47% identical to SessionStart, differing in 30 lines, and is treated as a copy.
Other hooks, from other repositories
PreToolUse
Runs before the agent uses a tool for Bash and Agent tool calls, running $HOME/.dotnet/tools/multiagent-setup hook block-dangerous (3 commands). From Neftedollar/multiagent-template.
PostToolUse
Runs after a tool call finishes for Edit, Write, WebSearch and WebFetch tool calls, running $HOME/.dotnet/tools/multiagent-setup hook auto-lint (2 commands). From Neftedollar/multiagent-template.
Stop
Runs when the agent finishes a response, running $HOME/.dotnet/tools/multiagent-setup hook stop-guard. From Neftedollar/multiagent-template.
Stop
Runs when the agent finishes a response, executing team-event.mjs via node. From VictorTomaili/agent-cli.
SessionEnd
Runs when a session ends, executing team-event.mjs via node. From VictorTomaili/agent-cli.
PostToolUse
Runs after a tool call finishes for Write and Edit tool calls, executing format_and_lint.sh. From supabase/supabase.