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 Borda/AI-Rig/plugin install developWrote 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/borda/ai-rig/pre-tool-use)<a href="https://agentmods.dev/hooks/borda/ai-rig/pre-tool-use"><img src="https://agentmods.dev/badge/hooks/borda/ai-rig/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": [
{
"hooks": [
{
"command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/enforce-review-header.js\"",
"type": "command"
}
],
"matcher": "AskUserQuestion"
},
{
"hooks": [
{
"command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/agent-router.js\"",
"statusMessage": "Routing agent",
"type": "command"
}
],
"matcher": "Agent"
},
{
"hooks": [
{
"command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/sentinel-read-allow.js\"",
"type": "command"
}
],
"matcher": "Bash"
},
{
"hooks": [
{
"command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/blueprint-allow.js\"",
"type": "command"
}
],
"matcher": "Bash"
},
{
"hooks": [
{
"command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/write-guard.js\"",
"type": "command"
}
],
"matcher": "Edit"
},
{
"hooks": [
{
"command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/write-guard.js\"",
"type": "command"
}
],
"matcher": "Write"
},
{
"hooks": [
{
"command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/write-guard.js\"",
"type": "command"
}
],
"matcher": "NotebookEdit"
}
]
}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 · 68 lines scan A 04dba14c6a68
PreToolUse is a hook published in the GitHub repository Borda/AI-Rig (25 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
SessionStart
Runs when a session starts on compact, executing post-compact-context.py, map-memory-finalize.py and map-memory-recall.py (3 commands). From azalio/map-framework.
UserPromptSubmit
Runs when you submit a prompt, before the agent sees it, executing license_prompt_guard.py and run_if_licensed.py via uv with --no-project, --python and --exec (3 commands). From maxritter/pilot-shell.
PreToolUse
Runs before the agent uses a tool for ^new_context$ tool calls, executing launch.py via python3. From hehee9/codex-compressor.
SubagentStart
Runs when a subagent starts, running an inline shell check. From goondocks-co/open-agent-kit.
PostToolUseFailure
Runs when a tool call fails, executing EventLogger.hook.ts and AlgorithmNudge.hook.ts (2 commands). From DorShaer/Husk.
PostToolUse
Runs after a tool call finishes for Edit and Write tool calls, executing format-ts.sh. From yu-iskw/coding-agent-fabric.