PostToolUse

PostToolUse is a hook for coding agents from kbichave/skills. Its token cost is not measured, scanned A, original, MIT.

An after-action hook that runs when the coding agent finishes a tool call. It runs Python scripts after Write and Edit actions, plus a context-monitoring script after tool calls.

In plain words
What is it for?
Use it for post-edit checks and for monitoring context after the agent uses tools.
Why use it?
It can perform follow-up checks after files change and monitor the agent's working context. This helps catch issues or track implementation details during development.

Hook

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the deep plugin — 4 skills, 16 agents, 6 hooks shipped together

One of 4 entries in hooks.json — they are configured in one file and arrive together.

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add kbichave/skills
Claude Code
/plugin install deep

Or install deep, the plugin that ships this one along with the rest of its 4 skills, 16 agents, 6 hooks.

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

agentmods badge for PostToolUse

README.md
[![agentmods](https://agentmods.dev/badge/hooks/kbichave/skills/post-tool-use.svg)](https://agentmods.dev/hooks/kbichave/skills/post-tool-use)
Your own site
<a href="https://agentmods.dev/hooks/kbichave/skills/post-tool-use"><img src="https://agentmods.dev/badge/hooks/kbichave/skills/post-tool-use.svg" alt="Measured on agentmods" height="20"></a>
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 3d 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 · 21 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Write|Edit",
      "hooks": [
        {
          "type": "command",
          "command": "python3 ${CLAUDE_PLUGIN_ROOT}/scripts/hooks/impl-post-tool-use.py"
        }
      ]
    },
    {
      "hooks": [
        {
          "type": "command",
          "command": "python3 ${CLAUDE_PLUGIN_ROOT}/scripts/hooks/deep-context-monitor.py"
        }
      ]
    }
  ]
}
Same file

What else hooks.json configures

This page is one entry in a file that holds 4. Installing the file brings all of them; each is measured and scanned on its own page.

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.

  1. 3d ago First seen · 21 lines scan A eceef919f5bb

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository kbichave/skills (2 stars, last pushed 4d 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.