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 rube-de/cc-skills/plugin install cdtWrote 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/rube-de/cc-skills/pre-tool-use)<a href="https://agentmods.dev/hooks/rube-de/cc-skills/pre-tool-use"><img src="https://agentmods.dev/badge/hooks/rube-de/cc-skills/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 8d 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.
This is a copy
56% identical to SessionStart — 34 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"PreToolUse": [
{
"matcher": "TeamCreate",
"hooks": [
{
"type": "command",
"command": "${CLAUDE_PLUGIN_ROOT}/scripts/check-agent-teams.sh"
},
{
"type": "command",
"command": "${CLAUDE_PLUGIN_ROOT}/scripts/track-team-state.sh create"
}
]
},
{
"matcher": "SendMessage",
"hooks": [
{
"type": "command",
"command": "${CLAUDE_PLUGIN_ROOT}/scripts/check-agent-teams.sh"
}
]
},
{
"matcher": "TeamDelete",
"hooks": [
{
"type": "command",
"command": "${CLAUDE_PLUGIN_ROOT}/scripts/check-agent-teams.sh"
},
{
"type": "command",
"command": "${CLAUDE_PLUGIN_ROOT}/scripts/track-team-state.sh delete"
}
]
}
]
}What else hooks.json configures
This page is one entry in a file that holds 4. 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.
- 8d ago First seen · 39 lines scan A 77df8c02919c
PreToolUse is a hook published in the GitHub repository rube-de/cc-skills (10 stars, last pushed yesterday), 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. It is 56% identical to SessionStart, differing in 34 lines, and is treated as a copy.
Other hooks, from other repositories
SessionStart
Runs when a session starts on startup and compact, executing session-context.sh (2 commands). From OrodruinLabs/nazgul.
PostToolUse
Runs after a tool call finishes for Edit, Write and MultiEdit tool calls, executing formatter.sh. From OrodruinLabs/nazgul.
SessionEnd
Runs when a session ends, executing session-staging.sh. From OrodruinLabs/nazgul.
TaskCompleted
Runs when a task is marked completed, executing task-completed.sh. From OrodruinLabs/nazgul.
SubagentStop
Runs when a subagent finishes, executing subagent-stop.sh. From OrodruinLabs/nazgul.
TeammateIdle
Runs on the TeammateIdle event, executing teammate-idle-guard.sh. From OrodruinLabs/nazgul.