agentmods.dev

PostToolUse

A hook that runs a command after a tool call finishes when the tool used is apply_patch, which edits files.

In plain words
What is it for?
Use it to run the configured cli.js post-tool-use check after apply_patch operations.
Why use it?
It automatically applies project-rule checks after file changes, reducing the chance that an edit leaves the project out of compliance.

Hook

11 4d ago A scan tokens not measured original MIT
View the source file code-yeongyu/codex-rules
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/code-yeongyu/codex-rules/post-tool-use
Clone the repo
git clone --depth 1 https://github.com/code-yeongyu/codex-rules
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 2d 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.

hooks/hooks.json · 15 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "^apply_patch$",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${PLUGIN_ROOT}/dist/cli.js\" hook post-tool-use",
          "timeout": 10,
          "statusMessage": "matching project rules"
        }
      ]
    }
  ]
}
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. 2d ago First seen · 15 lines scan A 58a1c220b27a

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository code-yeongyu/codex-rules (11 stars, last pushed 4d 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-30.

LanguagesSecurityagents-mdcodexcodex-plugincontext-injectionhooksrules
Related

Other hooks, from other repositories

SessionStart

Runs when a session starts on startup, resume and clear, executing run_component_hook.py via python3. From qingye-lab/rootloom.

qingye-lab/rootloom · not measured

PostToolUse

Runs after a tool call finishes, executing run.sh. From nikshepsvn/scrim.

nikshepsvn/scrim · not measured

BeforeTool

Runs on the BeforeTool event, running npx -y cc-safety-net hook --gemini-cli. From kenryu42/gemini-safety-net.

kenryu42/gemini-safety-net · not measured

PreToolUse

Runs before the agent uses a tool, executing govern.mjs. From agentic-control-plane/codex-acp-plugin.

agentic-control-plane/codex-acp-plugin · not measured

PostToolUse

Runs after a tool call finishes for Write, Edit and NotebookEdit tool calls, executing batou-hook.sh. From turenlabs/batou.

turenlabs/batou · not measured

PreCompact

Runs before the context is compacted, executing checkpoint.js via node. From yanfeid/claude-amber.

yanfeid/claude-amber · not measured