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/cloudai-x/claude-workflow-v2/pre-tool-usegit clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2Grade 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 yesterday.
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.
Copies of this mod
8 near-identical copies found in the catalogue:
- PostToolUse — 88% identical, 18 lines differ
- SessionEnd — 88% identical, 27 lines differ
- PreToolUse — 88% identical, 49 lines differ
- SessionEnd — 88% identical, 27 lines differ
- SessionEnd — 86% identical, 27 lines differ
- UserPromptSubmit — 84% identical, 29 lines differ
- PostCompact — 84% identical, 27 lines differ
- PreToolUse — 84% identical, 20 lines differ
What it actually says
{
"PreToolUse": [
{
"matcher": "Edit|Write",
"hooks": [
{
"type": "command",
"command": "python3 ${CLAUDE_PLUGIN_ROOT}/hooks/protect-files.py"
},
{
"type": "command",
"command": "python3 ${CLAUDE_PLUGIN_ROOT}/hooks/security-check.py"
},
{
"type": "command",
"command": "python3 ${CLAUDE_PLUGIN_ROOT}/hooks/pre-commit-check.py"
}
]
},
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "bash ${CLAUDE_PLUGIN_ROOT}/hooks/log-commands.sh"
},
{
"type": "command",
"command": "bash ${CLAUDE_PLUGIN_ROOT}/hooks/branch-protection.sh"
}
]
}
]
}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.
- yesterday First seen · 34 lines scan A 44a69cddf7d1
PreToolUse is a hook published in the GitHub repository CloudAI-X/claude-workflow-v2 (1,411 stars, last pushed 7d 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-30.
Other hooks, from other repositories
PreToolUse
Runs before the agent uses a tool for mcp__.*__(get_data_from_fields, get_sql_from_fields, initiate_analysis), mcp__.*__(create_object, update_object, create_entity, import_tables, create_context_item, update_context_item), mcp__.*__(list_entities, get_entity, get_field, search_model, list_databases, list_schemas…
Stop
Runs when the agent finishes a response, executing stop.sh via bash. From kage-core/Kage.
SubagentStop
Runs when a subagent finishes, executing observe.sh via bash. From kage-core/Kage.
SubagentStop
Runs when a subagent finishes, running observer hook claude-code subagent-stop. From superbasedapp/observer.
SubagentStart
Runs when a subagent starts, executing subagent-start.mjs via node. From Prismer-AI/PrismerCloud.
SessionStart
Runs when a session starts, running agent-recall-session-start. From mnardit/agent-recall.