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/kouroshez/coding-os/post-tool-use-failuregit clone --depth 1 https://github.com/kouroshez/coding-osWrote 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/kouroshez/coding-os/post-tool-use-failure)<a href="https://agentmods.dev/hooks/kouroshez/coding-os/post-tool-use-failure"><img src="https://agentmods.dev/badge/hooks/kouroshez/coding-os/post-tool-use-failure.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
PostToolUseFailure 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 today.
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.
What it actually says
{
"PostToolUseFailure": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "env COS_AGENT=claude \".claude/hooks/record-verify-auto.sh\"",
"statusMessage": "🧾 Recording failed suite result...",
"timeout": 15
},
{
"type": "command",
"command": "env COS_AGENT=claude \".claude/hooks/agent-presence.sh\"",
"timeout": 5
},
{
"type": "command",
"command": "env COS_AGENT=claude \".claude/hooks/capture-tool-failure.sh\"",
"timeout": 5
}
]
}
]
}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.
- today First seen · 25 lines scan A 686a022d0001
PostToolUseFailure is a hook published in the GitHub repository kouroshez/coding-os (6 stars, last pushed 3d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other hooks, from other repositories
SessionStart
Runs when a session starts, executing session-start.sh. From HKUDS/LightRAG.
SessionStart
Runs when a session starts, executing world-model-session.js via node. From SaravananJaichandar/world-model-mcp.
PreToolUse
Runs before the agent uses a tool for Bash, Edit, Write, MultiEdit and NotebookEdit tool calls, executing block-npm-publish.sh, block-unsafe-git.sh and block-generated-edit.sh (3 commands). From wlsdks/ontology-atlas.
SessionStart
Runs when a session starts, executing skeptic-suggest.sh via bash. From gambletan/cortex.
Stop
Runs when the agent finishes a response, executing contextdb-memory-hook.py via python3. From mikhailbovt/ContextDB-Codex.
SessionStart
Runs when a session starts, running agent-recall-session-start. From mnardit/agent-recall.