Prismer Cloud is an infrastructure layer for AI agents that provides shared learning, compressed context, persistent memory, collaboration, messaging, tasks, identity, and workspaces. It is for agents and the people building or using long-running agent systems that need information and outcomes to persist across sessions. The catalogue entries provide skills, hooks, agents, instructions, and a plugin for using Prismer Cloud.
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 Prismer-AI/PrismerCloud/plugin install claude-code-pluginWrote 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/prismer-ai/prismercloud/post-tool-use-failure)<a href="https://agentmods.dev/hooks/prismer-ai/prismercloud/post-tool-use-failure"><img src="https://agentmods.dev/badge/hooks/prismer-ai/prismercloud/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 7d 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": [
{
"matcher": "Bash|Edit|Write",
"hooks": [
{
"type": "command",
"command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/post-tool-failure.mjs\""
}
]
}
]
}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.
- 7d ago First seen · 13 lines scan A a3e95557edf1
PostToolUseFailure is a hook published in the GitHub repository Prismer-AI/PrismerCloud (1,410 stars, last pushed 1mo 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
Stop
Runs when the agent finishes a response, running echo '## 🧠 Memex Retro Reminder. From iamtouchskyer/memex.
UserPromptSubmit
Runs when you submit a prompt, before the agent sees it, running leteo hook user-prompt-submit. From asanabrial/leteo.
SessionEnd
Runs when a session ends, running leteo hook session-stop. From asanabrial/leteo.
SessionStart
Runs when a session starts, executing session-start.sh via bash. From kage-core/Kage.
PostToolUse
Runs after a tool call finishes, executing observe.sh via bash. From kage-core/Kage.
PostToolUseFailure
Runs when a tool call fails, executing observe.sh via bash. From kage-core/Kage.