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/ai-sdlc-framework/ai-sdlc/pre-tool-usegit clone --depth 1 https://github.com/ai-sdlc-framework/ai-sdlcWrote 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/ai-sdlc-framework/ai-sdlc/pre-tool-use)<a href="https://agentmods.dev/hooks/ai-sdlc-framework/ai-sdlc/pre-tool-use"><img src="https://agentmods.dev/badge/hooks/ai-sdlc-framework/ai-sdlc/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 4d 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": "Bash",
"hooks": [
{
"type": "command",
"command": "bash \"$CLAUDE_PROJECT_DIR/ai-sdlc-plugin/hooks/enforce-blocked-actions.sh\"",
"if": "Bash(*)",
"statusMessage": "Checking action policy..."
}
]
}
]
}What else settings.json configures
This page is one entry in a file that holds 5. 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.
- 4d ago First seen · 15 lines scan A aef364935b7a
PreToolUse is a hook published in the GitHub repository ai-sdlc-framework/ai-sdlc (100 stars, last pushed 10d ago), licensed Apache-2.0. 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
PostToolUse
Runs after a tool call finishes, executing track-usage.sh. From luna-prompts/skillnote.
SessionStart
Runs when a session starts, executing run.sh via sh. From vaaraio/vaara.
SessionEnd
Runs when a session ends for clear, prompt_input_exit, logout, resume, bypass_permissions_disabled and other tool calls, running an inline shell check. From QORIS-AI/knox.
PreToolUse
Runs before the agent uses a tool for Bash, shell_command, exec_command, unified_exec, apply_patch, Write and Edit tool calls, executing pre-tool-adapter.py via python3 (2 commands). From arbiterForge/codeArbiter.
UserPromptSubmit
Runs when you submit a prompt, before the agent sees it, executing prune-transcript.py and prompt-submit.py via python3 (2 commands). From arbiterForge/codeArbiter.
PreToolUse
Runs before the agent uses a tool for Edit, Write and Bash tool calls, executing pre-tool-use-guard.cjs via node. From metago-ai/metagolifeform.