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/notque/vexjoy-agent/stopgit clone --depth 1 https://github.com/notque/vexjoy-agentGrade 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 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
{
"Stop": [
{
"hooks": [
{
"type": "command",
"command": "python3 \"$HOME/.claude/hooks/session-summary.py\"",
"description": "Generate session summary and save metrics",
"timeout": 10000
},
{
"type": "command",
"command": "python3 \"$HOME/.claude/hooks/routing-outcome-stop-fallback.py\"",
"description": "Resolve still-pending routing outcomes at session end (autonomous runs with no next user turn)",
"timeout": 3000
},
{
"type": "command",
"command": "python3 \"$HOME/.claude/hooks/rules-distill-trigger.py\"",
"description": "Auto-trigger rules distillation every 7 days",
"timeout": 5000
},
{
"type": "command",
"command": "python3 \"$HOME/.claude/hooks/stop-drift-guard.py\"",
"description": "Advisory: re-wake the session when this session's changes introduce toolkit drift (hook smoke-test, doc-count, or routing-manifest drift) so it can be fixed before CI",
"timeout": 20000,
"asyncRewake": true,
"rewakeMessage": "Toolkit drift guard found drift in this session's changes — fix the drift below (or acknowledge it), then continue with the user's original request or continue waiting for their reply. This is supplementary, not a replacement for your previous response:",
"rewakeSummary": "Toolkit drift guard found drift to review"
}
]
}
]
}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 · 35 lines scan A 1322249468f8
Stop is a hook published in the GitHub repository notque/vexjoy-agent (417 stars, last pushed 2d 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 Edit and Write tool calls, executing validate-skill-on-edit.mjs via node. From jame581/GodotPrompter.
UserPromptSubmit
Runs when you submit a prompt, before the agent sees it, executing user-prompt-submit.sh and track-usage.sh (2 commands). From softspark/ai-toolkit.
SubagentStop
Runs when a subagent finishes, executing subagent-stop.sh. From softspark/ai-toolkit.
UserPromptSubmit
Runs when you submit a prompt, before the agent sees it for 为什么还是不行, 根本原因, 主要矛盾, 实践方案, 验证标准, 证据, 继续推进, 项目推进不动, 项目卡住, 开源, 没人用, research plan, root cause, primary contradiction, retrospective, experiment design, practice plan, validation criteria, evidence, no users, GitHub stars, open source and adoption tool calls…
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.