Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add NeoLi00/memX/plugin install memXWrote 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/neoli00/memx/post-tool-use-failure)<a href="https://agentmods.dev/hooks/neoli00/memx/post-tool-use-failure"><img src="https://agentmods.dev/badge/hooks/neoli00/memx/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.
What it actually says
{
"PostToolUseFailure": [
{
"hooks": [
{
"type": "command",
"command": "node \"${CLAUDE_PLUGIN_ROOT}/dist/.runtime/src/bin/memx-hook.mjs\" claude-code PostToolUseFailure",
"timeout": 8
}
]
}
]
}What else hooks.json configures
This page is one entry in a file that holds 12. Installing the file brings all of them; each is measured and scanned on its own page.
- Hook Notification 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 UserPromptSubmit 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 · 13 lines scan A 22243dedf102
PostToolUseFailure is a hook published in the GitHub repository NeoLi00/memX (407 stars, last pushed 3mo 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, Read and Bash tool calls, executing block-dist.sh, enforce-bun.sh and no-truncated-schema-proof.sh via bash with --show-toplevel (3 commands). From lobu-ai/lobu.
SessionStart
Runs when a session starts, running mem context --project "$PWD" --limit 10 --format brief. From runtimenoteslabs/memory-layer.
SessionEnd
Runs when a session ends, running an inline shell check. From runtimenoteslabs/memory-layer.
PostToolUse
Runs after a tool call finishes for Write and Edit tool calls, executing format_and_lint.sh. From supabase/supabase.
SessionStart
Runs when a session starts, executing on-start.js via node. From google-gemini/gemini-cli.
SessionStart
Runs when a session starts on startup, executing install_pkgs.sh. From supabase/supabase.