A tool-use hook that runs a Python script after selected agent actions finish, including shell commands, file reads, edits, and MCP calls. MCP is a standard way for an agent to use external tools.

It is for sending completed tool-use events to the trigger-tree script after matching actions.

It automatically records or processes activity across many agent actions, instead of requiring separate manual tracking.

PostToolUse — Hook by Hedde

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/hedde/trigger_tree/post-tool-use

Clone the repo

git clone --depth 1 https://github.com/Hedde/trigger_tree

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 84% copy Near-identical to another mod 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 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.

Origin

This is a copy

84% identical to SessionStart — 3 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.

hooks/hooks.json · 15 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Bash|Read|Glob|Grep|Skill|apply_patch|Edit|Write|mcp__.*",
      "hooks": [
        {
          "type": "command",
          "command": "H=\"${CLAUDE_PLUGIN_ROOT}/scripts/tt-codex-hook.py\"; [ -f \"$H\" ] || exit 0; if command -v python3 >/dev/null 2>&1; then exec python3 \"$H\" --client codex; else exec python \"$H\" --client codex; fi",
          "commandWindows": "if exist \"%CLAUDE_PLUGIN_ROOT%\\scripts\\tt-codex-hook.py\" py -3 \"%CLAUDE_PLUGIN_ROOT%\\scripts\\tt-codex-hook.py\" --client codex",
          "timeout": 5
        }
      ]
    }
  ]
}

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.

yesterday First seen · 15 lines scan A 11d055581348

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository Hedde/trigger_tree (14 stars, last pushed 8d 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 84% identical to SessionStart, differing in 3 lines, and is treated as a copy.

Analytics and metrics Languages Writing and docs claude-code claude-code-plugin docs-as-code documentation observability telemetry

PostToolUse

Getting it into your agent

Grade A, and why

Nothing flagged

This is a copy

What it actually says

What this file has done since we first saw it

Other hooks, from other repositories

PostToolUse

SessionEnd

PostToolUse

SessionStart

SessionStart

PreToolUse