agentmods.dev

SubagentStop

An automatic action that runs a JavaScript command when a coding subagent finishes.

In plain words
What is it for?
Use it to run the configured subagent-finished script after each subagent stops. The input does not say what that script does.
Why use it?
It lets a project respond consistently whenever a subagent completes work, without relying on someone to trigger the action manually.

Hook

1 2mo ago A scan tokens not measured copy · 86% MIT
View the source file bitqs/Slime
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/bitqs/slime/subagent-stop
Clone the repo
git clone --depth 1 https://github.com/bitqs/Slime
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 86% copy Near-identical to another mod in the catalogue.
Security

Grade A, and why

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

Origin

This is a copy

86% identical to UserPromptSubmit — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

hooks/hooks.json · 13 lines

What it actually says

{
  "SubagentStop": [
    {
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/hook-subagentstop.js\"",
          "timeout": 2
        }
      ]
    }
  ]
}
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. yesterday First seen · 13 lines scan A bbe15241ef8a

Subscribe to this mod's changes

SubagentStop is a hook published in the GitHub repository bitqs/Slime (1 stars, last pushed 2mo 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. It is 86% identical to UserPromptSubmit, differing in 4 lines, and is treated as a copy.

Building agentsLanguagesclaude-codeclaude-code-plugingamificationhookspixijsrpg
Related

Other hooks, from other repositories

SubagentStart

Runs when a subagent starts, executing subagent-brief.js via node. From V-Songbird/hush.

V-Songbird/hush · not measured

SubagentStart

Runs when a subagent starts, executing subagent-tracker.js via node. From NYCU-Chung/cc-statusline.

NYCU-Chung/cc-statusline · not measured

SubagentStart

Runs when a subagent starts, running node. From V-Songbird/razor.

V-Songbird/razor · not measured

SubagentStop

Runs when a subagent finishes, executing stop-gate.sh. From rennf93/opus-fable-playbook.

rennf93/opus-fable-playbook · not measured

SubagentStop

Runs when a subagent finishes, running node. From Keonho-Chu/menhera-loop.

Keonho-Chu/menhera-loop · not measured

SubagentStop

Runs when a subagent finishes, executing log-subagent-activity.py. From ryanzhao1011/workframe.

ryanzhao1011/workframe · not measured