agentmods.dev

PostToolUse

A post-tool hook is an automatic command that runs after a coding agent finishes a Skill tool call.

In plain words
What is it for?
It runs the plugin's usage-logging script after each matching Skill call.
Why use it?
It records Skill usage without requiring a separate manual step.

Hook

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

plugins/coding-discipline/hooks/hooks.json · 13 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Skill",
      "hooks": [
        {
          "type": "command",
          "command": "\"${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.cmd\" log-usage"
        }
      ]
    }
  ]
}
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 11f533b5e432

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository chipfighter/coding-discipline (6 stars, last pushed 1mo 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.

Code reviewagent-skillsai-agentsai-codinganthropicclaude-codeclaude-code-plugin
Related

Other hooks, from other repositories

PostToolUse

Runs after a tool call finishes, executing wmux-bridge.mjs via node. From openwong2kim/wmux.

openwong2kim/wmux · not measured

SessionEnd

Runs when a session ends, executing session-lifecycle-hook.mjs via node. From sendbird/cc-plugin-codex.

sendbird/cc-plugin-codex · not measured

PreToolUse

Runs before the agent uses a tool for Bash, Write, Edit, Bash, Task, Task and Agent tool calls, executing run-py.sh and context-warning.sh via bash (4 commands). From primeline-ai/evolving-lite.

primeline-ai/evolving-lite · not measured

SubagentStop

Runs when a subagent finishes, executing subagent_stop.py via uv. From sepehrbayat/SEPCC.

sepehrbayat/SEPCC · not measured

PreCompact

Runs before the context is compacted, running an inline shell check. From zalom/plastic.

zalom/plastic · not measured

SessionStart

Runs when a session starts, executing update-check.js via node. From KevinZai/commander.

KevinZai/commander · not measured