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/konamgil/mandu/post-tool-usegit clone --depth 1 https://github.com/konamgil/manduWrote 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/konamgil/mandu/post-tool-use)<a href="https://agentmods.dev/hooks/konamgil/mandu/post-tool-use"><img src="https://agentmods.dev/badge/hooks/konamgil/mandu/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": "Edit|Write",
"hooks": [
{
"type": "command",
"command": "node -e \"const p=process.env.FILE_PATH||'';if(p.includes('spec/contracts/')){process.stdout.write('Contract modified. Run: bunx mandu guard contract --validate')}\" 2>/dev/null || true"
}
],
"description": "Notify when contract files are modified"
}
]
}What else settings.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 · 14 lines scan A 747299382f34
PostToolUse is a hook published in the GitHub repository konamgil/mandu (46 stars, last pushed 7d ago), licensed MPL-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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other hooks, from other repositories
SessionStart
Runs when a session starts on startup and resume, running bun run hook:session-start. From archgate/cli.
WorktreeCreate
Runs when a git worktree is created, running bun run hook:worktree-create. From archgate/cli.
PostToolUse
Runs after a tool call finishes for Write and Edit tool calls, running bun run hook:format-file. From archgate/cli.
UserPromptSubmit
Runs when you submit a prompt, before the agent sees it, running an inline shell check. From coleam00/Archon.
SessionStart
Runs when a session starts, running clens-hook SessionStart. From silouone/clens.
PostToolUse
Runs after a tool call finishes for Write and Edit tool calls, executing format_and_lint.sh. From supabase/supabase.