Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/hooks/billbai-longarena/termite-protocol/post-tool-use)<a href="https://agentmods.dev/hooks/billbai-longarena/termite-protocol/post-tool-use"><img src="https://agentmods.dev/badge/hooks/billbai-longarena/termite-protocol/post-tool-use/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/hooks/billbai-longarena/termite-protocol/post-tool-use"><img src="https://agentmods.dev/badge/hooks/billbai-longarena/termite-protocol/post-tool-use.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 2mo 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- Stop — 86% identical, 15 lines differ
- PostToolUse — 75% identical, 15 lines differ
What it actually says
{
"PostToolUse": [
{
"matcher": "Write|Edit",
"hooks": [
{
"type": "command",
"command": "bash ${CLAUDE_PLUGIN_ROOT}/scripts/hook-post-edit.sh",
"timeout": 10
}
]
},
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "bash ${CLAUDE_PLUGIN_ROOT}/scripts/hook-post-commit.sh",
"timeout": 10
}
]
}
]
}What else hooks.json configures
This page is one entry in a file that holds 6. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 2mo ago First seen · 24 lines scan A 29680aaccacf
PostToolUse is a hook published in the GitHub repository billbai-longarena/Termite-Protocol (11 stars, last pushed 2mo 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.
Other hooks, from other repositories
PreToolUse
Runs before the agent uses a tool for Edit, Write, MultiEdit and Bash tool calls, running mneme-hook. From MnemeHQ/mneme.
SessionStart
Runs when a session starts, running mneme-hook. From MnemeHQ/mneme.
PreToolUse
Runs before the agent uses a tool for Edit, Write and Read tool calls, running uvx --from rekal==3.4.0 rekal hook block-memory-writes (2 commands). From janbjorge/rekal.
UserPromptSubmit
Runs when you submit a prompt, before the agent sees it, running uvx --from rekal==3.4.0 rekal hook user-prompt-submit. From janbjorge/rekal.
SessionStart
Runs when a session starts, running uvx --from rekal==3.4.0 rekal hook session-start. From janbjorge/rekal.
Stop
Runs when the agent finishes a response, running mneme-hook. From MnemeHQ/mneme.