What is SubagentStop?

A set of rules for choosing GPU targets in NPA workbench tools. It covers training, rendering, inference, workflow files, and direct Kubernetes jobs.

Use it when selecting a GPU family, changing workflow resources, routing images, or reviewing where a job should run. It helps encode GPU type and count in CLI options, SDK settings, or YAML.

It helps match the hardware to the workload and avoid treating ordinary runtime or application errors as GPU-placement problems. The choice is kept consistent across commands, configuration, and workflow resources.

SubagentStop — Hook by fusengine

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/fusengine/agents/subagent-stop

Clone the repo

git clone --depth 1 https://github.com/fusengine/agents

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

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 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/ai-pilot/hooks/hooks.json · 14 lines

What it actually says

{
  "SubagentStop": [
    {
      "_description": "Single matcher-'' entry (Python parity: check-solid-from-transcript ran with matcher '' for EVERY agent). The dispatcher (onSubagentStop) routes internally: research-expert -> doc cache, sniper -> lessons + test caches, then the universal SOLID transcript check for all agents. Per-agent entries here would both narrow the SOLID check AND double-fire the cache writers.",
      "matcher": "",
      "hooks": [
        {
          "type": "command",
          "command": "bun $HOME/.claude/plugins/marketplaces/fusengine-plugins/plugins/node_modules/@fusengine/harness/dist/cli/bin.mjs hook claude-code aipilot"
        }
      ]
    }
  ]
}

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.

2d ago First seen · 14 lines scan A f2a7add18a5f

Subscribe to this mod's changes

SubagentStop is a hook published in the GitHub repository fusengine/agents (25 stars, last pushed 29d 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.

Building agents DevOps and cloud Productivity claude-agent claude-agents claude-code claude-code-plugin claude-skills claudecode

SubagentStop

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other hooks, from other repositories

SubagentStart

SubagentStop

SubagentStop

SubagentStop

SubagentStop

SubagentStop