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/zenml-io/zenml/pre-tool-usegit clone --depth 1 https://github.com/zenml-io/zenmlWrote 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/zenml-io/zenml/pre-tool-use)<a href="https://agentmods.dev/hooks/zenml-io/zenml/pre-tool-use"><img src="https://agentmods.dev/badge/hooks/zenml-io/zenml/pre-tool-use.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
PreToolUse 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
{
"PreToolUse": [
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "if echo \"$CLAUDE_TOOL_INPUT\" | jq -r '.command' 2>/dev/null | grep -q 'git commit'; then echo '🔍 Running pre-commit formatting...'; bash \"$CLAUDE_PROJECT_DIR\"/scripts/format.sh && echo '✅ Formatting complete' || { echo '❌ Formatting failed - commit blocked'; exit 1; }; fi",
"timeout": 300
}
]
}
]
}What else settings.json configures
This page is one entry in a file that holds 2. 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 c47b68e53912
PreToolUse is a hook published in the GitHub repository zenml-io/zenml (5,575 stars, last pushed today), licensed Apache-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
SubagentStart
Runs when a subagent starts, executing log_agent_metrics.py via uv. From streamlit/streamlit.
PostToolUse
Runs after a tool call finishes for Edit and Write tool calls, executing post_edit_autofix.sh. From streamlit/streamlit.
PermissionDenied
Runs on the PermissionDenied event, running TOKKI_LAUNCHER_NO_UPDATE=1 tokki hooks claude-ingest --event. From ThalesGroup/agilab.
PermissionRequest
Runs when the agent asks permission for an action, running TOKKI_LAUNCHER_NO_UPDATE=1 tokki hooks claude-ingest --event. From ThalesGroup/agilab.
PostToolUseFailure
Runs when a tool call fails, running TOKKI_LAUNCHER_NO_UPDATE=1 tokki hooks claude-ingest --event. From ThalesGroup/agilab.
PreToolUse
Runs before the agent uses a tool, running TOKKI_LAUNCHER_NO_UPDATE=1 tokki hooks claude-ingest --event. From ThalesGroup/agilab.