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.
git clone --depth 1 https://github.com/JanYork/llm-wiki-cliWrote 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/janyork/llm-wiki-cli/post-tool-use-failure)<a href="https://agentmods.dev/hooks/janyork/llm-wiki-cli/post-tool-use-failure"><img src="https://agentmods.dev/badge/hooks/janyork/llm-wiki-cli/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 2d 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
89% identical to PostToolUse — 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": "lwc --scope all agent hook --agent claude --event PostToolUseFailure",
"timeout": 2,
"statusMessage": "Refreshing bounded LWC context..."
}
]
}
]
}What else hooks.json configures
This page is one entry in a file that holds 7. 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.
- 2d ago First seen · 14 lines scan A 622dcb8b994a
PostToolUseFailure is a hook published in the GitHub repository JanYork/llm-wiki-cli (52 stars, last pushed yesterday), 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 89% identical to PostToolUse, differing in 4 lines, and is treated as a copy.
Other hooks, from other repositories
SessionStart
Runs when a session starts, executing on-start.js via node. From google-gemini/gemini-cli.
PreToolUse
Runs before the agent uses a tool for Bash tool calls, running an inline shell check. From apache/superset.
PreToolUse
Runs before the agent uses a tool, executing pre-write.sh and pre-bash.sh (2 commands). From anthropics/claude-cookbooks.
PreCompact
Runs before the context is compacted for manual and auto tool calls, executing hook-handler.cjs via node (4 commands). From ruvnet/RuView.
SessionStart
Runs when a session starts on startup, clear and compact, executing run-hook.cmd. From obra/superpowers.
SessionStart
Runs when a session starts, executing hook-handler.cjs and auto-memory-hook.mjs via node (2 commands). From ruvnet/RuView.