A group of post-tool hooks that runs the same Bash script after selected memory, shell, file-writing, and file-editing actions finish.

It is for running post-tool-use.sh after Gitmem recall or search, Bash, Write, and Edit operations.

It lets the agent apply a follow-up check automatically after those actions instead of doing it by hand.

PostToolUse — Hook by gitmem-dev

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/gitmem-dev/gitmem/post-tool-use

Clone the repo

git clone --depth 1 https://github.com/gitmem-dev/gitmem

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/hooks.json · 54 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "mcp__gitmem__recall",
      "hooks": [
        {
          "type": "command",
          "command": "bash ${CLAUDE_PLUGIN_ROOT}/scripts/post-tool-use.sh",
          "timeout": 3000
        }
      ]
    },
    {
      "matcher": "mcp__gitmem__search",
      "hooks": [
        {
          "type": "command",
          "command": "bash ${CLAUDE_PLUGIN_ROOT}/scripts/post-tool-use.sh",
          "timeout": 3000
        }
      ]
    },
    {
      "matcher": "Bash",
      "hooks": [
        {
          "type": "command",
          "command": "bash ${CLAUDE_PLUGIN_ROOT}/scripts/post-tool-use.sh",
          "timeout": 3000
        }
      ]
    },
    {
      "matcher": "Write",
      "hooks": [
        {
          "type": "command",
          "command": "bash ${CLAUDE_PLUGIN_ROOT}/scripts/post-tool-use.sh",
          "timeout": 3000
        }
      ]
    },
    {
      "matcher": "Edit",
      "hooks": [
        {
          "type": "command",
          "command": "bash ${CLAUDE_PLUGIN_ROOT}/scripts/post-tool-use.sh",
          "timeout": 3000
        }
      ]
    }
  ]
}

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 · 54 lines scan A 3d4b4cd5b3b1

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository gitmem-dev/gitmem (9 stars, last pushed 23d 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.

Memory and context Research Writing and docs agentic-ai ai ai-agents claude-code institutional-memory mcp

PostToolUse

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other hooks, from other repositories

Setup

SessionStart

Stop

PreToolUse

PostCompact

StopFailure