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/thalesgroup/agilab/post-tool-use-failuregit clone --depth 1 https://github.com/ThalesGroup/agilabWrote 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/thalesgroup/agilab/post-tool-use-failure)<a href="https://agentmods.dev/hooks/thalesgroup/agilab/post-tool-use-failure"><img src="https://agentmods.dev/badge/hooks/thalesgroup/agilab/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 5d 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 else settings.json configures
This page is one entry in a file that holds 16. Installing the file brings all of them; each is measured and scanned on its own page.
- Settings file agilab A not measured
- Hook Notification A not measured
- Hook PermissionDenied A not measured
- Hook PermissionRequest A not measured
- Hook PostCompact 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 StopFailure A not measured
- Hook SubagentStart A not measured
- Hook SubagentStop 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.
- 5d ago First seen · 13 lines scan A e9059f747a53
PostToolUseFailure is a hook published in the GitHub repository ThalesGroup/agilab (21 stars, last pushed today), 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-30.
Other hooks, from other repositories
PreToolUse
Runs before the agent uses a tool for Skill and Bash tool calls, executing log_agent_metrics.py and pre_bash_redirect.py via uv (2 commands). From streamlit/streamlit.
SubagentStart
Runs when a subagent starts, executing log_agent_metrics.py via uv. From streamlit/streamlit.
PreToolUse
Runs before the agent uses a tool for Bash tool calls, executing format.sh. From zenml-io/zenml.
PostToolUse
Runs after a tool call finishes for Edit and Write tool calls, executing post_edit_autofix.sh. From streamlit/streamlit.
Stop
Runs when the agent finishes a response, executing stop_check.sh. From streamlit/streamlit.
Stop
Runs when the agent finishes a response, running swarm claude agent-stop. From joelhooks/swarm-tools.