agentmods.dev

PostToolUse

An after-use hook that runs a Node.js script when a coding-agent tool call finishes.

In plain words
What is it for?
Recording or handling what happened after the agent uses a tool.
Why use it?
It lets agentmemory process each completed tool call automatically after it happens.

Hook

28k 8d ago A scan tokens not measured original Apache-2.0
View the source file rohitg00/agentmemory
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/rohitg00/agentmemory/post-tool-use
Clone the repo
git clone --depth 1 https://github.com/rohitg00/agentmemory
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.

Origin

Copies of this mod

5 near-identical copies found in the catalogue:

plugin/hooks/hooks.json · 12 lines

What it actually says

{
  "PostToolUse": [
    {
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/post-tool-use.mjs\""
        }
      ]
    }
  ]
}
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. yesterday First seen · 12 lines scan A 611918157f62

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository rohitg00/agentmemory (27,776 stars, last pushed 8d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

agentmemoryagentsaiclaudeclaudecodecodex
Related

Other hooks, from other repositories

PreToolUse

Runs before the agent uses a tool for Bash, Write and Write tool calls, running an inline shell check (3 commands). From Justdvp/claude-code-templates.

Justdvp/claude-code-templates · not measured

UserPromptSubmit

Runs when you submit a prompt, before the agent sees it, running node. From cortadel/cortadel.

cortadel/cortadel · not measured

SessionStart

Runs when a session starts, running agent-recall-session-start. From mnardit/agent-recall.

mnardit/agent-recall · not measured

SubagentStop

Runs when a subagent finishes, executing tlc-cleanup.sh and continuous-execution-hook.sh via bash (2 commands). From johanolofsson72/Claude.

johanolofsson72/Claude · not measured

PostToolUse

Runs after a tool call finishes for Write and Edit tool calls, executing format_and_lint.sh. From supabase/supabase.

supabase/supabase · not measured

SessionStart

Runs when a session starts on startup, executing install_pkgs.sh. From supabase/supabase.

supabase/supabase · not measured