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 azmym/gemini-plugin/plugin install gemini-pluginWrote 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/azmym/gemini-plugin/pre-tool-use)<a href="https://agentmods.dev/hooks/azmym/gemini-plugin/pre-tool-use"><img src="https://agentmods.dev/badge/hooks/azmym/gemini-plugin/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 3d 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": "${CLAUDE_PLUGIN_ROOT}/hooks/pre-destructive-bash.sh",
"async": false
}
]
},
{
"matcher": "ExitPlanMode",
"hooks": [
{
"type": "command",
"command": "${CLAUDE_PLUGIN_ROOT}/hooks/plan-complete.sh",
"async": false
}
]
}
]
}What else hooks.json configures
This page is one entry in a file that holds 7. 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.
- 3d ago First seen · 24 lines scan A d4fb1c17cdfe
PreToolUse is a hook published in the GitHub repository azmym/gemini-plugin (1 stars, last pushed 20d 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
PreToolUse
Runs before the agent uses a tool for Read, Edit and Write tool calls, executing block_secrets.py via python3. From winstonkoh87/Athena-Public.
SessionStart
Runs when a session starts, executing check_env.py via python. From Ibrahim-3d/nano-banana-claude-plugin.
SessionStart
Runs when a session starts, executing session-lifecycle-hook.mjs via node. From markbrutx/gemini-plugin-cc.
Stop
Runs when the agent finishes a response, executing stop-review-gate-hook.mjs via node. From markbrutx/gemini-plugin-cc.
PreToolUse
Runs before the agent uses a tool for ExitPlanMode, Task and Write tool calls, executing plan-peer-review-check.sh, task-peer-review-check.sh and write-peer-review-check.sh via bash (3 commands). From slb350/gemini-peer-review.
UserPromptSubmit
Runs when you submit a prompt, before the agent sees it, executing user-prompt-check.sh via bash. From slb350/gemini-peer-review.