agentmods.dev

PostToolUse

An automatic reminder that runs after code-editing tools finish. It tells the agent to save project-specific conventions as persistent memories for future sessions.

In plain words
What is it for?
It is for projects using AgentMemory, where decisions, preferences, or constraints should be stored after files are edited.
Why use it?
It helps prevent useful coding conventions from being forgotten between sessions. The reminder also reduces the need to repeat the same project guidance.

Hook

2 3mo ago A scan tokens not measured original MIT
View the source file Obidel/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/obidel/agentmemory/post-tool-use
Clone the repo
git clone --depth 1 https://github.com/Obidel/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.

hooks/hooks.json · 13 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Edit|Write|MultiEdit",
      "hooks": [
        {
          "type": "command",
          "command": "echo 'Tip: project-specific conventions should be stored as memories via AgentMemory MCP add_memory. Future sessions will pick them up automatically.'"
        }
      ]
    }
  ]
}
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 · 13 lines scan A 633a19b49136

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository Obidel/Agentmemory (2 stars, last pushed 3mo 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 AIFrontendMemory and contextai-agentsclaudecursormcpmodel-context-protocol
Related

Other hooks, from other repositories

PostToolUse

Runs after a tool call finishes for Write, Edit, Write and Edit tool calls, running an inline shell check (2 commands). From soumyachk101/VibeLens.

soumyachk101/VibeLens · not measured

PreToolUse

Runs before the agent uses a tool, executing blekline-pre-tool-use.sh. From Blekline/blekline-oss.

Blekline/blekline-oss · not measured

PostToolUse

Runs after a tool call finishes, executing blekline-post-tool-use.sh. From Blekline/blekline-oss.

Blekline/blekline-oss · 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

SessionStart

Runs when a session starts, executing on-start.js via node. From google-gemini/gemini-cli.

google-gemini/gemini-cli · not measured