agentmods.dev

Stop

A stop hook that runs a shell script when the coding agent finishes replying.

In plain words
What is it for?
Running cleanup, logging, notifications, or other tasks defined in stop-hook.sh.
Why use it?
It lets you perform an automatic final action after every agent response without running the script yourself.

Hook

13 2mo ago A scan tokens not measured no licence
View the source file colliery-io/metis
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/colliery-io/metis/stop
Clone the repo
git clone --depth 1 https://github.com/colliery-io/metis
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 unknown 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.

plugins/metis/hooks/hooks.json · 13 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 332d07adf4f0

Subscribe to this mod's changes

Stop is a hook published in the GitHub repository colliery-io/metis (13 stars, last pushed 2mo ago), with no licence file. 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.

Data and AILanguagesProject managementai-agentsclidelivery-toolskanbanmcpmodel-context-protocol
Related

Other hooks, from other repositories

PostToolUse

Runs after a tool call finishes for task_claim, mcp__.*__task_claim, task_deliver, mcp__.*__task_deliver, task_release, mcp__.*__task_release, task_deliver and mcp__.*__task_deliver tool calls, executing claim-guard.mjs and post-deliver.mjs via node (2 commands). From ustoppble/overclick.

ustoppble/overclick · not measured

Stop

Runs when the agent finishes a response, executing stop-guard.mjs via node. From ustoppble/overclick.

ustoppble/overclick · not measured

SessionStart

Runs when a session starts, running flux ready --json. From sirsjg/flux.

sirsjg/flux · not measured

SessionStart

Runs when a session starts on startup, resume and compact, executing on-session-start.sh. From Chorus-AIDLC/Chorus.

Chorus-AIDLC/Chorus · not measured

TeammateIdle

Runs on the TeammateIdle event, executing on-teammate-idle.sh. From Chorus-AIDLC/Chorus.

Chorus-AIDLC/Chorus · not measured

TaskCompleted

Runs when a task is marked completed, executing on-task-completed.sh. From Chorus-AIDLC/Chorus.

Chorus-AIDLC/Chorus · not measured