Post-action checks that run after the agent reads, searches, or edits files. They check for unsaved changes after reading or searching and read diagnostics after edits.

Use it in projects where agent file operations should be followed by unsaved-change checks or VS Code diagnostics.

It helps reveal unsaved editor changes and code problems introduced by an edit.

PostToolUse — Hook by mend3

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/mend3/vscode-agent-bridge/post-tool-use

Clone the repo

git clone --depth 1 https://github.com/mend3/vscode-agent-bridge

Or install vscode-bridge, the plugin that ships this one along with the rest of its 2 skills, 3 hooks, 1 MCP server.

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.

packages/plugin/hooks/hooks.json · 26 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Read|Grep|Glob",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/unsaved-warning.mjs\"",
          "timeout": 8,
          "statusMessage": "checking for unsaved changes"
        }
      ]
    },
    {
      "matcher": "Edit|Write|MultiEdit",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/after-edit-diagnostics.mjs\"",
          "timeout": 15,
          "statusMessage": "reading diagnostics"
        }
      ]
    }
  ]
}

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 · 26 lines scan A fe3c3d720251

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository mend3/vscode-agent-bridge (0 stars, last pushed 22d 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.

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

PostToolUse

SessionStart

SessionStart

PreToolUse

PreToolUse

SessionStart