A hook that runs an asynchronous shell script after the agent finishes Read, Edit, Write, or Bash tool calls. It uses a tool-tracker script to record those activities.

Use it to track Read, Edit, Write, and Bash operations through Patrol’s post-action script.

It keeps a record of important file-reading, file-editing, file-writing, and shell actions after they happen. This can support Patrol’s checks without delaying the next agent action.

PostToolUse — Hook by cukas

Install

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.

agentmods

npx agentmods add hooks/cukas/patrol/post-tool-use

Clone the repo

git clone --depth 1 https://github.com/cukas/patrol

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

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 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.

hooks/hooks.json · 15 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Read|Edit|Write|Bash",
      "hooks": [
        {
          "type": "command",
          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/tool-tracker.sh",
          "timeout": 5,
          "async": true
        }
      ]
    }
  ]
}

Changes

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 · 15 lines scan A ab145faa5eb8

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository cukas/patrol (3 stars, last pushed 5mo 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-31.

Code review Debugging claude-code claude-code-plugin claude-code-plugins code-quality debugg developer-tools

PreToolUse

Runs before the agent uses a tool for Bash, Write, Edit and MultiEdit tool calls, executing run-hook.cmd (5 commands). From greglas75/zuvo.

greglas75/zuvo · not measured

PreToolUse

Runs before the agent uses a tool for Write and Edit tool calls, executing validate-plugin.sh. From ivan-magda/claude-code-plugin-template.

ivan-magda/claude-code-plugin-template · not measured

PreToolUse

Runs before the agent uses a tool for Bash, Read, Write, Edit, Glob, Grep, mcp__.*, Bash, Task, Write and Edit tool calls, executing dispatch.cjs, pre-dispatch-conflict-check.cjs, mcp-call-gate.cjs, commit-attribution.cjs, task-track-model.cjs, security-critical-warn.cjs and phase-checkpoint.cjs via node (8 commands).…

nguyenthienthanh/aura-frog · not measured

PostToolUse

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other hooks, from other repositories

PreToolUse

PreToolUse

PreToolUse

SessionStart

SessionStart

PostToolUse