A collection of post-tool hooks that run commands after actions such as writing files, editing files, running shell commands, or leaving a plan. The listed hooks synchronize memory, record changes, capture plans, and prompt for session notes.

Use it to trigger memory indexing, changelog updates, plan capture, and session-note reminders after the configured tool calls.

It automates project housekeeping after development actions, so important changes and plans are less likely to go unrecorded.

PostToolUse — Hook by hamchowderr

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/hamchowderr/braynee/post-tool-use

Clone the repo

git clone --depth 1 https://github.com/hamchowderr/braynee

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 original 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 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.

hooks/hooks.json · 163 lines

How it starts

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

{
  "PostToolUse": [
    {
      "matcher": "Write",
      "hooks": [
        {
          "type": "command",
          "command": "node",
          "args": [
            "${CLAUDE_PLUGIN_ROOT}/hooks/memory-index-sync.js"
          ],
          "timeout": 15
        }
      ]
    },
    {
      "matcher": "Write|Edit",
      "hooks": [
        {
          "type": "command",
          "command": "node",
          "args": [
            "${CLAUDE_PLUGIN_ROOT}/hooks/vault-changelog.js"
          ],
          "timeout": 60,
          "async": true
        }
      ]
    },
    {
      "matcher": "ExitPlanMode",
      "hooks": [
        {
          "type": "command",
          "command": "node",
          "args": [
            "${CLAUDE_PLUGIN_ROOT}/hooks/plan-capture.js"
          ],
          "timeout": 60,
          "async": true
        }
      ]
    },
    {
      "matcher": "Write|Edit|Bash|PowerShell",
      "hooks": [
        {
          "type": "command",
          "command": "node",
          "args": [
            "${CLAUDE_PLUGIN_ROOT}/hooks/session-note-nudge.js"
          ],
          "timeout": 15
        },
        {
          "type": "command",
          "command": "node",
          "args": [
            "${CLAUDE_PLUGIN_ROOT}/hooks/statusline-state.js"
          ],
          "timeout": 60,
          "async": true
        }
      ]
    },
    {
      "matcher": "Bash|PowerShell",
      "hooks": [
        {
          "type": "command",
          "command": "node",
          "args": [
            "${CLAUDE_PLUGIN_ROOT}/hooks/commit-cadence-nudge.js"
          ],
          "timeout": 60,
          "async": true
        }
      ]
    },
    {
      "matcher": "Bash|PowerShell",
      "hooks": [
        {
          "type": "command",
          "command": "node",
          "args": [
            "${CLAUDE_PLUGIN_ROOT}/hooks/beads-claim-to-branch.js"
          ],
          "timeout": 60,
          "async": true
        }
      ]
    },
    {
      "matcher": "Bash|P

Read the full file on GitHub · 163 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 · 163 lines scan A a7bd2b34264c

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository hamchowderr/braynee (2 stars, last pushed 6d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Data and AI Git and workflow Memory and context

PostToolUse

Getting it into your agent

Grade A, and why

Nothing flagged

How it starts

What this file has done since we first saw it

Other hooks, from other repositories

PostToolUse

SessionStart

SessionStart

PreToolUse

SessionStart

SessionStart