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/yunbow/ai-dev-os-plugin-claude-code/pre-tool-usegit clone --depth 1 https://github.com/yunbow/ai-dev-os-plugin-claude-codeGrade 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 2d 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": "Write|Edit",
"hooks": [
{
"type": "command",
"command": "bash -c 'INPUT=$(cat); FILE=$(echo \"$INPUT\" | jq -r \".tool_input.file_path // .tool_input.file_path\"); if echo \"$FILE\" | grep -qE \"(node_modules|dist|build|\\.next|__pycache__|\\.venv|vendor|\\.git)/|\\.(lock|svg|png|jpg|jpeg|gif|ico|woff|woff2|ttf|eot)$\"; then exit 0; fi; if echo \"$FILE\" | grep -qE \"\\.(ts|tsx|js|jsx|py|go)$\"; then echo \"{\\\"additionalContext\\\": \\\"AI Dev OS: Ensure this change complies with the project guidelines. Check CLAUDE.md for the applicable rules.\\\"}\"; fi'",
"statusMessage": "AI Dev OS: Guideline check..."
}
]
},
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "bash -c 'INPUT=$(cat); CMD=$(echo \"$INPUT\" | jq -r \".tool_input.command\"); if echo \"$CMD\" | grep -qE \"^git commit\"; then echo \"{\\\"additionalContext\\\": \\\"Please run a guideline check before committing: /ai-dev-os-check\\\"}\"; fi'",
"statusMessage": "AI Dev OS: Pre-commit check..."
}
]
}
]
}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.
- 2d ago First seen · 24 lines scan A 4d97f509fdeb
PreToolUse is a hook published in the GitHub repository yunbow/ai-dev-os-plugin-claude-code (2 stars, last pushed 5mo 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 Edit and Write tool calls, running an inline shell check. From codeverbojan/claude-code-kickstart.
SessionStart
Runs when a session starts, executing session-primer.sh. From codeverbojan/claude-code-kickstart.
PostToolUse
Runs after a tool call finishes for Bash tool calls, executing capture-signal.sh. From codeverbojan/claude-code-kickstart.
UserPromptSubmit
Runs when you submit a prompt, before the agent sees it, executing habits-coach.sh. From codeverbojan/claude-code-kickstart.
PreToolUse
Runs before the agent uses a tool for Write and Edit tool calls, executing validate_workflow_write.py via python. From IronRookieCoder/auto-pilot.
Stop
Runs when the agent finishes a response, executing verify-gate.sh. From codeverbojan/claude-code-kickstart.