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 ladiossoop5star/open_magi/plugin install open-magiWrote 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/ladiossoop5star/open_magi/post-tool-use)<a href="https://agentmods.dev/hooks/ladiossoop5star/open_magi/post-tool-use"><img src="https://agentmods.dev/badge/hooks/ladiossoop5star/open_magi/post-tool-use.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
PostToolUse 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
{
"PostToolUse": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "sh -c 'if [ -n \"${CLAUDE_PLUGIN_ROOT:-}\" ] && [ -x \"${CLAUDE_PLUGIN_ROOT}/hooks/magi-tool-reminder\" ]; then exec \"${CLAUDE_PLUGIN_ROOT}/hooks/magi-tool-reminder\"; fi; exit 0'",
"timeout": 5,
"statusMessage": "Checking Magi contract"
}
]
}
]
}What else hooks.json configures
This page is one entry in a file that holds 3. 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.
- 4d ago First seen · 15 lines scan A dcac078b8f47
PostToolUse is a hook published in the GitHub repository ladiossoop5star/open_magi (3 stars, last pushed 7d 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-31.
Other hooks, from other repositories
PostToolUse
Runs after a tool call finishes for hivemind_find, mcp__plugin_swarm_swarm-tools__hivemind_find, skills_use, Skill, swarmmail_init, mcp__plugin_swarm_swarm-tools__swarmmail_init, hivemind_store, mcp__plugin_swarm_swarm-tools__hivemind_store, swarm_complete and TaskUpdate tool calls, running swarm claude track-tool…
SessionStart
Runs when a session starts, running swarm claude session-start. From joelhooks/swarm-tools.
SubagentStop
Runs when a subagent finishes, running swarm claude subagent-stop. From joelhooks/swarm-tools.
Stop
Runs when the agent finishes a response, running swarm claude agent-stop. From joelhooks/swarm-tools.
PreCompact
Runs before the context is compacted, running swarm claude pre-compact. From joelhooks/swarm-tools.
PostToolUse
Runs after a tool call finishes for Write and Edit tool calls, executing format_and_lint.sh. From supabase/supabase.