A set of automatic actions that run after command-line or file-editing tools finish. It includes actions for events such as creating a pull request, completing a build, or changing files.

Use it to log pull-request links, analyze completed builds, and run quality checks after Bash commands or file edits.

It removes repetitive follow-up work and can run checks or reminders automatically after common development actions. Some configured checks run in the background so they do not block the task.

PostToolUse — Hook by zhmxiaowo

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/zhmxiaowo/opencode-simple/post-tool-use

Clone the repo

git clone --depth 1 https://github.com/zhmxiaowo/opencode-simple

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 86% 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

86% identical to PreToolUse — 70 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 · 80 lines

How it starts

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

{
  "PostToolUse": [
    {
      "matcher": "Bash",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/hooks/run-with-flags.js\" \"post:bash:pr-created\" \"scripts/hooks/post-bash-pr-created.js\" \"standard,strict\""
        }
      ],
      "description": "Log PR URL and provide review command after PR creation"
    },
    {
      "matcher": "Bash",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/hooks/run-with-flags.js\" \"post:bash:build-complete\" \"scripts/hooks/post-bash-build-complete.js\" \"standard,strict\"",
          "async": true,
          "timeout": 30
        }
      ],
      "description": "Example: async hook for build analysis (runs in background without blocking)"
    },
    {
      "matcher": "Edit|Write|MultiEdit",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/hooks/run-with-flags.js\" \"post:quality-gate\" \"scripts/hooks/quality-gate.js\" \"standard,strict\"",
          "async": true,
          "timeout": 30
        }
      ],
      "description": "Run quality gate checks after file edits"
    },
    {
      "matcher": "Edit",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/hooks/run-with-flags.js\" \"post:edit:format\" \"scripts/hooks/post-edit-format.js\" \"standard,strict\""
        }
      ],
      "description": "Auto-format JS/TS files after edits (auto-detects Biome or Prettier)"
    },
    {
      "matcher": "Edit",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/hooks/run-with-flags.js\" \"post:edit:typecheck\" \"scripts/hooks/post-edit-typecheck.js\" \"standard,strict\""
        }
      ],
      "description": "TypeScript check after editing .ts/.tsx files"
    },
    {
      "matcher": "Edit",
      "hook

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

yesterday First seen · 80 lines scan A 786391529765

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository zhmxiaowo/opencode-simple (2 stars, last pushed 5mo 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 86% identical to PreToolUse, differing in 70 lines, and is treated as a copy.

Code review

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