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/edobreque/clens/post-tool-use-failuregit clone --depth 1 https://github.com/edobreque/clensWrote 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/edobreque/clens/post-tool-use-failure)<a href="https://agentmods.dev/hooks/edobreque/clens/post-tool-use-failure"><img src="https://agentmods.dev/badge/hooks/edobreque/clens/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 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
81% identical to UserPromptSubmit — 4 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
{
"PostToolUseFailure": [
{
"hooks": [
{
"type": "command",
"command": "clens-hook PostToolUseFailure"
}
]
}
]
}What else hooks.json configures
This page is one entry in a file that holds 17. Installing the file brings all of them; each is measured and scanned on its own page.
- Hook ConfigChange A not measured
- Hook Notification A not measured
- Hook PermissionRequest A not measured
- Hook PostToolUse A not measured
- Hook PreCompact A not measured
- Hook PreToolUse A not measured
- Hook SessionEnd A not measured
- Hook SessionStart A not measured
- Hook Stop A not measured
- Hook SubagentStart A not measured
- Hook SubagentStop A not measured
- Hook TaskCompleted A not measured
- Hook TeammateIdle A not measured
- Hook UserPromptSubmit A not measured
- Hook WorktreeCreate A not measured
- Hook WorktreeRemove A not measured
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 · 12 lines scan A 9083487bd8dd
PostToolUseFailure is a hook published in the GitHub repository edobreque/clens (2 stars, last pushed yesterday), 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. It is 81% identical to UserPromptSubmit, differing in 4 lines, and is treated as a copy.
Other hooks, from other repositories
SessionStart
Runs when a session starts, running clens-hook SessionStart. From silouone/clens.
SessionEnd
Runs when a session ends, running clens-hook SessionEnd. From silouone/clens.
UserPromptSubmit
Runs when you submit a prompt, before the agent sees it, running clens-hook UserPromptSubmit. From silouone/clens.
PreToolUse
Runs before the agent uses a tool, running clens-hook PreToolUse. From silouone/clens.
PostToolUse
Runs after a tool call finishes, running clens-hook PostToolUse. From silouone/clens.
Notification
Runs when the agent sends a notification, running clens-hook Notification. From silouone/clens.