PostToolUse

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

Runs after a tool call finishes for Agent, mcp__*, Read, Bash, Grep, Glob, Write, Edit, Bash, Agent, TaskUpdate, TaskCreate, Skill, Bash, Write, Edit, Agent, TaskUpdate, TaskCreate, Skill, NotebookEdit, Read, Grep, Glob, WebFetch and WebSearch tool calls, running node (28 commands). From yonatangross/orchestkit.

Hook

Runs only inside a plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else, and the catalogue could not identify which plugin ships it.

Install

Getting it into your agent

There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.

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/yonatangross/orchestkit/post-tool-use.svg)](https://agentmods.dev/hooks/yonatangross/orchestkit/post-tool-use)
Your own site
<a href="https://agentmods.dev/hooks/yonatangross/orchestkit/post-tool-use"><img src="https://agentmods.dev/badge/hooks/yonatangross/orchestkit/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 unknown 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 today.

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.

plugins/ork/hooks/hooks.json · 331 lines

How it starts

The opening of the file, as written. The whole thing — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.

{
  "PostToolUse": [
    {
      "matcher": "Agent",
      "hooks": [
        {
          "type": "command",
          "command": "node",
          "async": true,
          "timeout": 5,
          "args": [
            "${CLAUDE_PLUGIN_ROOT}/hooks/bin/run-hook.mjs",
            "posttool/task/agent-task-auto-register"
          ]
        },
        {
          "type": "command",
          "command": "node",
          "async": true,
          "timeout": 15,
          "args": [
            "${CLAUDE_PLUGIN_ROOT}/hooks/bin/run-hook.mjs",
            "lifecycle/webhook-forwarder"
          ]
        }
      ]
    },
    {
      "matcher": "mcp__*",
      "hooks": [
        {
          "type": "command",
          "command": "node",
          "timeout": 5,
          "statusMessage": "Processing MCP result...",
          "args": [
            "${CLAUDE_PLUGIN_ROOT}/hooks/bin/run-hook.mjs",
            "posttool/mcp-output-transform"
          ]
        },
        {
          "type": "command",
          "command": "node",
          "async": true,
          "timeout": 15,
          "args": [
            "${CLAUDE_PLUGIN_ROOT}/hooks/bin/run-hook.mjs",
            "lifecycle/webhook-forwarder"
          ]
        }
      ]
    },
    {
      "matcher": "Read|Bash|Grep|Glob",
      "hooks": [
        {
          "type": "command",
          "command": "node",
          "timeout": 5,
          "statusMessage": "Scanning for secrets...",
          "args": [
            "${CLAUDE_PLUGIN_ROOT}/hooks/bin/run-hook.mjs",
            "posttool/secret-handler"
          ]
        }
      ]
    },
    {
      "matcher": "Write|Edit",
      "hooks": [
        {
          "type": "command",
          "command": "node",
          "timeout": 10,
          "statusMessage": "Formatting...",
          "args": [
            "${CLAUDE_PLUGIN_ROOT}/hooks/bin/run-hook.mjs",
            "posttool/auto-lint"
          ]
        },
        {
          "type": "command",
          "command": "node",

Read the full file on GitHub · 331 lines

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. today First seen · 331 lines scan A b50979523546

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed today), 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-09-03.