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/dinhnguyenngoc/spec-driven-claude-code/stopgit clone --depth 1 https://github.com/dinhnguyenngoc/spec-driven-claude-codeWrote 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/dinhnguyenngoc/spec-driven-claude-code/stop)<a href="https://agentmods.dev/hooks/dinhnguyenngoc/spec-driven-claude-code/stop"><img src="https://agentmods.dev/badge/hooks/dinhnguyenngoc/spec-driven-claude-code/stop.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
Stop 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 3d 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
{
"Stop": [
{
"hooks": [
{
"type": "command",
"command": "python3 ${CLAUDE_PROJECT_DIR}/.claude/hooks/log-command-stats.py"
}
]
}
]
}What else settings.json configures
This page is one entry in a file that holds 2. 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.
- 3d ago First seen · 12 lines scan A f20d2f815b45
Stop is a hook published in the GitHub repository dinhnguyenngoc/spec-driven-claude-code (20 stars, last pushed 4d 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
PostToolUse
Runs after a tool call finishes for Write, Edit, MultiEdit and Bash tool calls, executing dnp-di-registration-check.js, dnp-project-scope-guard.js, dnp-post-edit-format.js and dnp-build-verify.js via node (4 commands). From zdanovichnick/dotnet-pilot.
SessionStart
Runs when a session starts on startup, resume, clear and compact, executing dnp-statusline-sync.js via node. From zdanovichnick/dotnet-pilot.
PreToolUse
Runs before the agent uses a tool for Read, Write, Edit, MultiEdit, Bash, Grep, Glob, Agent, mcp__.*code-analyzer.*, Write, Edit and Bash tool calls, executing dnp-sync-global-claude-md.js, dnp-dotnet-priority.js, dnp-code-analyzer-redirect.js, dnp-migration-guard.js, dnp-git-autoapprove.js and dnp-commit-format.js…
UserPromptSubmit
Runs when you submit a prompt, before the agent sees it, executing license_prompt_guard.py and run_if_licensed.py via uv with --no-project, --python and --exec (3 commands). From maxritter/pilot-shell.
SubagentStop
Runs when a subagent finishes, running an inline shell check. From MostAshraf/ai-sdlc-harness.
Stop
Runs when the agent finishes a response, executing preflight_audit.sh via bash. From sgaabdu4/building-flutter-apps.