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.
npx agentmods add hooks/serradura/okf/post-tool-usegit clone --depth 1 https://github.com/serradura/okfWrote 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/serradura/okf/post-tool-use)<a href="https://agentmods.dev/hooks/serradura/okf/post-tool-use"><img src="https://agentmods.dev/badge/hooks/serradura/okf/post-tool-use.svg" alt="Measured on agentmods" 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 4d 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.
This is a copy
44% identical to SessionStart — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"PostToolUse": [
{
"matcher": "Edit|Write|MultiEdit",
"hooks": [
{
"type": "command",
"command": "\"$CLAUDE_PROJECT_DIR\"/.claude/hooks/run post-edit"
}
]
}
]
}What else settings.json configures
This page is one entry in a file that holds 5. 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.
- 4d ago First seen · 13 lines scan A a7e8cb85cbcf
PostToolUse is a hook published in the GitHub repository serradura/okf (142 stars, last pushed 9d 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. It is 44% identical to SessionStart, differing in 8 lines, and is treated as a copy.
Other hooks, from other repositories
Stop
Runs when the agent finishes a response, executing stop-checklist.ts via node with --disable-warning and --experimental-strip-types. From breferrari/obsidian-mind.
PostToolUse
Runs after a tool call finishes for Write, Edit and MultiEdit tool calls, executing validate-raw-source.sh and qmd-reindex.sh (2 commands). From johnfkoo951/cmds-llm-wiki.
Stop
Runs when the agent finishes a response, executing auto_save_session.sh via bash. From walm00/business-context-os.
PreCompact
Runs before the context is compacted, executing precompact_save.sh via bash. From walm00/business-context-os.
PreCompact
Runs before the context is compacted, running an inline shell check. From nickroci/ultan.
SubagentStop
Runs when a subagent finishes, executing run-custom.mjs via node. From livewithlively/lively.