Stop

End-of-response hooks that run three Node.js commands when an agent finishes replying. The commands dispatch handoff and rate-limit checks, record session metrics, and refresh context.

In plain words
What is it for?
Running response-finish checks, recording session data, and refreshing the agent's context after a task response.
Why use it?
They automate cleanup and session bookkeeping after each response, so these checks do not depend on someone remembering to run them.

Hook

Part of the aura-frog plugin — 17 skills, 24 commands, 15 agents, 10 hooks, 6 MCP servers shipped together

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/nguyenthienthanh/aura-frog/stop
Clone the repo
git clone --depth 1 https://github.com/nguyenthienthanh/aura-frog

Or install aura-frog, the plugin that ships this one along with the rest of its 17 skills, 24 commands, 15 agents, 10 hooks, 6 MCP servers.

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

aura-frog/hooks/hooks.json · 22 lines

What it actually says

{
  "Stop": [
    {
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/dispatch.cjs\" '>compact-handoff' '>rate-limit-check'"
        },
        {
          "type": "command",
          "async": true,
          "command": ". \"${CLAUDE_PLUGIN_ROOT}/scripts/envrc-guarded-source.sh\"; node \"${CLAUDE_PLUGIN_ROOT}/hooks/session-metrics.cjs\" 2>&1"
        },
        {
          "type": "command",
          "async": true,
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/hooks/context-auto-refresh.cjs\" 2>&1"
        }
      ]
    }
  ]
}
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. 3d ago First seen · 22 lines scan A 874018d94a17

Subscribe to this mod's changes

Stop is a hook published in the GitHub repository nguyenthienthanh/aura-frog (24 stars, last pushed 9d 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.