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 ChrisMckerracher/claude-dream-team/plugin install dream-teamWrote 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/chrismckerracher/claude-dream-team/pre-tool-use)<a href="https://agentmods.dev/hooks/chrismckerracher/claude-dream-team/pre-tool-use"><img src="https://agentmods.dev/badge/hooks/chrismckerracher/claude-dream-team/pre-tool-use/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/hooks/chrismckerracher/claude-dream-team/pre-tool-use"><img src="https://agentmods.dev/badge/hooks/chrismckerracher/claude-dream-team/pre-tool-use.svg" alt="Reviewed on agentmods" width="80" 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"PreToolUse": [
{
"matcher": "Task",
"hooks": [
{
"type": "prompt",
"prompt": "Check if this Task tool call is spawning a dream-team agent (subagent_type contains 'dream-team:'). If it is, enforce model assignment: dream-team:architect MUST use model 'opus'. All others (dream-team:product, dream-team:qa, dream-team:coding, dream-team:code-review, dream-team:ui-ux-designer) MUST use model 'sonnet'. If the model parameter is missing or set to the wrong value, BLOCK the call and tell the agent to re-issue it with the correct model parameter. If this is not a dream-team agent spawn, or the model is correct, respond with 'proceed'."
}
]
},
{
"matcher": "Bash",
"hooks": [
{
"type": "prompt",
"prompt": "If this Bash command involves 'git worktree add' or 'git worktree remove', verify that: (1) The worktree directory follows the convention ../worktrees/{agent-name}-task-{id}, (2) A feature branch will be created (not working directly on the epic branch), (3) The worktree doesn't already exist. If all checks pass or the command is not worktree-related, respond with 'proceed'. If there's an issue, explain what needs to change."
}
]
},
{
"matcher": "Bash",
"hooks": [
{
"type": "prompt",
"prompt": "If this Bash command involves 'git push --force' or 'git reset --hard' or 'git clean -f', BLOCK the command and explain that destructive git operations require explicit user confirmation. Respond with 'proceed' for all other commands."
}
]
},
{
"matcher": "TaskCreate",
"hooks": [
{
"type": "prompt",
"prompt": "Check if this TaskCreate call is creating a task that will be assigned to a coding agent. Indicators: the description mentions implementation, coding, writing code, building, fixing bugs, or is clearly a development task (not planning, design, reviWhat else hooks.json configures
This page is one entry in a file that holds 3. 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.
- 10d ago First seen · 60 lines scan A d935f56da5dc
PreToolUse is a hook published in the GitHub repository ChrisMckerracher/claude-dream-team (5 stars, last pushed 6mo 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
PostToolUse
Runs after a tool call finishes for Write and Edit tool calls, executing format_and_lint.sh. From supabase/supabase.
SessionStart
Runs when a session starts on startup, executing install_pkgs.sh. From supabase/supabase.
SessionStart
Runs when a session starts, executing on-start.js via node. From google-gemini/gemini-cli.
PreToolUse
Runs before the agent uses a tool for Bash tool calls, running an inline shell check. From apache/superset.
PreToolUse
Runs before the agent uses a tool, executing pre-write.sh and pre-bash.sh (2 commands). From anthropics/claude-cookbooks.
PreToolUse
Runs before the agent uses a tool for Bash tool calls, executing enforce-tools.mjs via node. From prisma/orm.