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/ard1102/ip-intelligence/pre-tool-usegit clone --depth 1 https://github.com/ard1102/ip-intelligenceGrade 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.
What it actually says
{
"PreToolUse": [
{
"matcher": "Grep",
"hooks": [
{
"type": "command",
"command": "echo '{\"decision\": \"block\", \"reason\": \"Use codebase-memory-mcp instead of Grep. Call mcp__codebase-memory-mcp__search_code for text/pattern search, or mcp__codebase-memory-mcp__search_graph for finding functions, classes, and routes by name or query.\"}'",
"shell": "bash"
}
]
},
{
"matcher": "Write(.*\\.py$)|Edit(.*\\.py$)",
"hooks": [
{
"type": "agent",
"prompt": "A Python file is about to be written or edited. The tool input contains the file path in the 'file_path' or 'path' key. Check if a corresponding test file exists in tests/: look for tests/test_{basename_without_ext}.py. Report: (1) test file path checked, (2) exists yes/no, (3) if yes — run 'pytest {test_path} -q --tb=no 2>&1 | tail -3' and report pass/fail count, (4) if no — note that writing production code without tests violates TDD. Do NOT block the write — report only.",
"timeout": 30000
}
]
}
]
}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 · 24 lines scan A 647e08aa1676
PreToolUse is a hook published in the GitHub repository ard1102/ip-intelligence (0 stars, last pushed 1mo 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, executing pre-write.sh and pre-bash.sh (2 commands). From anthropics/claude-cookbooks.
SessionStart
Runs when a session starts, executing session-start.sh. From anthropics/claude-cookbooks.
SessionStart
Runs when a session starts on startup, clear and compact, executing run-hook.cmd. From obra/superpowers.