PostToolUse

PostToolUse is a hook for Claude Code from baek-labs/hames. Its token cost is not measured, scanned A, a copy of PreToolUse, MIT.

A set of automatic checks that runs after editing files or using certain tools. The checks verify edits and tasks, update permissions, record contract evidence, and log the session.

In plain words
What is it for?
Use it in a project where file changes need validation, task tracking, permission updates, evidence records, or session logs.
Why use it?
It removes the need to remember these checks and records manually after each change. It also helps detect issues immediately after a tool finishes.

Hook for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: names the NotebookEdit tool.

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 hames plugin — 6 skills, 3 hooks shipped together

One of 3 entries in hooks.json upstream. Installing this one merges just its entry into your config; the other 2 are separate, each on its own page.

Good fit Use it in a project where file changes need validation, task tracking, permission updates, evidence records, or session logs.

Compare 6 hooks from other repositories ↓
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 baek-labs/hames
Claude Code
/plugin install hames

Made for: Claude Code.

Or install hames, the plugin that ships this one along with the rest of its 6 skills, 3 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/baek-labs/hames/post-tool-use/github.svg)](https://agentmods.dev/hooks/baek-labs/hames/post-tool-use)
Your own site
<a href="https://agentmods.dev/hooks/baek-labs/hames/post-tool-use"><img src="https://agentmods.dev/badge/hooks/baek-labs/hames/post-tool-use/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for PostToolUse

Your own site · 80×15
<a href="https://agentmods.dev/hooks/baek-labs/hames/post-tool-use"><img src="https://agentmods.dev/badge/hooks/baek-labs/hames/post-tool-use.svg" alt="Reviewed on agentmods" width="80" 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. A grade says what 26 rules found in the file — not that it is safe.
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 28d 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

86% identical to PreToolUse — 19 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.

packages/claude/hooks/hooks.json · 26 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "*",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/evidence-guard.js\"",
          "timeout": 10,
          "statusMessage": "Recording Hames evidence metadata"
        }
      ]
    },
    {
      "matcher": "Write|Edit|MultiEdit|NotebookEdit|apply_patch",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/index-sync.js\"",
          "timeout": 15,
          "statusMessage": "Updating the workspace index"
        }
      ]
    }
  ]
}
Same file

What else hooks.json configures

This page is one entry in a file that holds 3. 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. 28d ago Changed · +11 lines 7e0e54740ea5
  2. 1mo ago Changed · -36 lines d80f035a2e85
  3. 1mo ago First seen · 51 lines scan A e9217586f63d

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository baek-labs/hames (5 stars, last pushed 28d 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 19 lines, and is treated as a copy.