An automatic action that runs after selected coding-agent tools finish, such as creating teams, assigning tasks, or sending messages. It starts a Node.js orchestration script.

It helps coordinate agent teams, tasks, planning, tool searches, and web searches after each operation.

It removes the need to manually trigger follow-up coordination after these tools complete.

PostToolUse — Hook by hellowind777

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/hellowind777/hello2cc/post-tool-use

Clone the repo

git clone --depth 1 https://github.com/hellowind777/hello2cc

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

Origin

This is a copy

59% identical to SessionStart — 139 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 · 144 lines

How it starts

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

{
  "PostToolUse": [
    {
      "matcher": "TeamCreate",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/orchestrator.mjs\" post-tool-use",
          "timeout": 5
        }
      ]
    },
    {
      "matcher": "TeamDelete",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/orchestrator.mjs\" post-tool-use",
          "timeout": 5
        }
      ]
    },
    {
      "matcher": "Agent",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/orchestrator.mjs\" post-tool-use",
          "timeout": 5
        }
      ]
    },
    {
      "matcher": "Task",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/orchestrator.mjs\" post-tool-use",
          "timeout": 5
        }
      ]
    },
    {
      "matcher": "SendMessage",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/orchestrator.mjs\" post-tool-use",
          "timeout": 5
        }
      ]
    },
    {
      "matcher": "TaskCreate",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/orchestrator.mjs\" post-tool-use",
          "timeout": 5
        }
      ]
    },
    {
      "matcher": "TaskList",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/orchestrator.mjs\" post-tool-use",
          "timeout": 5
        }
      ]
    },
    {
      "matcher": "TaskGet",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/orchestrator.mjs\" post-tool-use",
          "timeout": 5
        }
      ]
    },
    {
      "matcher": "TaskUpdate",
      "hooks": [
        {
          "type": "command",
          "command":

Read the full file on GitHub · 144 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.

2d ago First seen · 144 lines scan A 6c593be7e647

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository hellowind777/hello2cc (694 stars, last pushed 3mo ago), licensed Apache-2.0. 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 59% identical to SessionStart, differing in 139 lines, and is treated as a copy.

Planning Research

PostToolUse

Getting it into your agent

Grade A, and why

Nothing flagged

This is a copy

How it starts

What this file has done since we first saw it

Other hooks, from other repositories

PostToolUse

SessionStart

SessionStart

PreToolUse

SessionStart

SessionStart