agentmods.dev

Stop

An automatic end-of-response hook that runs a shell script whenever the agent finishes replying.

In plain words
What is it for?
Use it to run the project's proof-log-session.sh script after every agent response.
Why use it?
It records a proof log for each completed session without requiring a separate manual command.

Hook

19 4d ago A scan tokens not measured original MIT
View the source file yurukusa/claude-code-hooks
Install

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.

agentmods
npx agentmods add hooks/yurukusa/claude-code-hooks/stop
Clone the repo
git clone --depth 1 https://github.com/yurukusa/claude-code-hooks
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

hooks/hooks.json · 13 lines

What it actually says

{
  "Stop": [
    {
      "matcher": "",
      "hooks": [
        {
          "type": "command",
          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/proof-log-session.sh"
        }
      ]
    }
  ]
}
Changes

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.

  1. 2d ago First seen · 13 lines scan A 7da32e8b9e02

Subscribe to this mod's changes

Stop is a hook published in the GitHub repository yurukusa/claude-code-hooks (19 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.

AI SafetyAutonomousbashclaude-codehookssafety
Related

Other hooks, from other repositories

PreToolUse

Runs before the agent uses a tool for Bash tool calls, executing bouncer.js. From karanb192/bouncer.

karanb192/bouncer · not measured

PreToolUse

Runs before the agent uses a tool for Bash, Bash, Bash, Write, Edit, Bash and Bash tool calls, executing move-delete-sequence-guard.sh and system-dir-protection-guard.sh with --force-with-lease (6 commands). From yurukusa/cc-safe-setup.

yurukusa/cc-safe-setup · not measured

PreToolUse

Runs before the agent uses a tool for mcp__memory__compact tool calls, executing trigger.sh. From cstelmach/terminal-agent-visual-signals.

cstelmach/terminal-agent-visual-signals · not measured

UserPromptSubmit

Runs when you submit a prompt, before the agent sees it, executing trigger.sh. From cstelmach/terminal-agent-visual-signals.

cstelmach/terminal-agent-visual-signals · not measured

Stop

Runs when the agent finishes a response, executing trigger.sh. From cstelmach/terminal-agent-visual-signals.

cstelmach/terminal-agent-visual-signals · not measured

SessionEnd

Runs when a session ends, executing trigger.sh. From cstelmach/terminal-agent-visual-signals.

cstelmach/terminal-agent-visual-signals · not measured