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/borda/vision-delivery/post-tool-usegit clone --depth 1 https://github.com/Borda/vision-deliveryWrote 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/borda/vision-delivery/post-tool-use)<a href="https://agentmods.dev/hooks/borda/vision-delivery/post-tool-use"><img src="https://agentmods.dev/badge/hooks/borda/vision-delivery/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": [
{
"hooks": [
{
"command": "node \"${PLUGIN_ROOT}/hooks/cta.js\"",
"commandWindows": "node \"$env:PLUGIN_ROOT\\hooks\\cta.js\"",
"type": "command"
}
],
"matcher": "^mcp__(plugin_[A-Za-z0-9_-]+_)?roboflow__.*$"
}
]
}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 · 14 lines scan A 9e46b4ed8382
PostToolUse is a hook published in the GitHub repository Borda/vision-delivery (4 stars, last pushed 23d ago), 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-31.
Other hooks, from other repositories
PostToolUse
Runs after a tool call finishes for TodoWrite, TaskCreate, TaskUpdate, TaskList, Write, Edit, MultiEdit, Bash, rp, RepoPrompt, Task and Agent tool calls, executing todo_tracker.py, edit_tracker.py and handoff_result.py via python3 (3 commands). From TerenceLiu98/prewalk.
SubagentStart
Runs when a subagent starts for ^(prewalk:)?prewalk-executor$ tool calls, executing handoff_lifecycle.py via python3. From TerenceLiu98/prewalk.
SubagentStop
Runs when a subagent finishes for ^(prewalk:)?prewalk-executor$ tool calls, executing handoff_lifecycle.py via python3. From TerenceLiu98/prewalk.
PostToolUseFailure
Runs when a tool call fails for Task and Agent tool calls, executing handoff_result.py via python3. From TerenceLiu98/prewalk.
PermissionDenied
Runs on the PermissionDenied event for Task and Agent tool calls, executing handoff_result.py via python3. From TerenceLiu98/prewalk.
PreToolUse
Runs before the agent uses a tool for Task and Agent tool calls, executing handoff_router.py via python3. From TerenceLiu98/prewalk.