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/lucianum7/repo-brainWrote 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/lucianum7/repo-brain/post-tool-use)<a href="https://agentmods.dev/hooks/lucianum7/repo-brain/post-tool-use"><img src="https://agentmods.dev/badge/hooks/lucianum7/repo-brain/post-tool-use/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/hooks/lucianum7/repo-brain/post-tool-use"><img src="https://agentmods.dev/badge/hooks/lucianum7/repo-brain/post-tool-use.svg" alt="Reviewed on agentmods" width="80" 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 9d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 9d ago First seen · 22 lines scan A a83f2eb8323a
PostToolUse is a hook published in the GitHub repository lucianum7/repo-brain (0 stars, last pushed 2d ago), with no licence file. 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
SessionEnd
Runs when a session ends, running leteo hook session-stop. From asanabrial/leteo.
SessionStart
Runs when a session starts, executing _run_hook.sh via bash. From lemoncrow-lab/lemoncrow.
UserPromptSubmit
Runs when you submit a prompt, before the agent sees it, executing _run_hook.sh via bash. From lemoncrow-lab/lemoncrow.
UserPromptExpansion
Runs to expand your prompt before the agent sees it, running an inline shell check. From TwoWells/Catenary.
PermissionDenied
Runs on the PermissionDenied event, running an inline shell check. From TwoWells/Catenary.
UserPromptSubmit
Runs when you submit a prompt, before the agent sees it, executing marrow-watch.sh. From aryawidjaja/marrow.