agentmods.dev

SubagentStop

A hook that runs when a subagent finishes and executes a JavaScript file with Node.js, a runtime for JavaScript programs.

In plain words
What is it for?
It is for running record-exploration.js after a subagent finishes in the VisFlow plugin.
Why use it?
It automates a follow-up action after a subagent completes, rather than requiring a person to start it.

Hook

33 25d ago A scan tokens not measured no licence
View the source file VisFlow/visflow-plugin
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/visflow/visflow-plugin/subagent-stop
Clone the repo
git clone --depth 1 https://github.com/VisFlow/visflow-plugin
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

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.

hooks/hooks.json · 12 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. yesterday First seen · 12 lines scan A 3285653de211

Subscribe to this mod's changes

SubagentStop is a hook published in the GitHub repository VisFlow/visflow-plugin (33 stars, last pushed 25d 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.

Building agentsLanguages
Related

Other hooks, from other repositories

SubagentStop

Runs when a subagent finishes, executing subagent-stop.sh. From softspark/ai-toolkit.

softspark/ai-toolkit · not measured

SubagentStop

Runs when a subagent finishes, executing cc10x_event_logger.py via python3. From romiluz13/cc10x.

romiluz13/cc10x · not measured

SubagentStop

Runs when a subagent finishes, executing memx-hook.mjs via node. From NeoLi00/memX.

NeoLi00/memX · not measured

Stop

Runs when the agent finishes a response, executing dag-tripwire.py and ledger-tripwire.py via python3 (2 commands). From Buckeyes22/subagent-model-routing.

Buckeyes22/subagent-model-routing · not measured

SubagentStart

Runs when a subagent starts, executing agent-state-reporter.js via node. From bjornjee/agent-dashboard.

bjornjee/agent-dashboard · not measured

SubagentStop

Runs when a subagent finishes, running an inline shell check. From ArdurAI/ardur.

ArdurAI/ardur · not measured