SubagentStart

A hook configuration that runs a Node.js script when an Explore, Plan, or general-purpose subagent starts.

In plain words
What is it for?
Use it to trigger subagent-context.mjs at the start of those subagent types, if the referenced plugin script is available.
Why use it?
It provides a defined startup action for different kinds of subagents. The input does not explain what the script changes or produces.

Hook

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/hellowind777/hello2cc/subagent-start
Clone the repo
git clone --depth 1 https://github.com/hellowind777/hello2cc
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 53% copy Near-identical to another mod in the catalogue.
Security

Grade A, and why

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

Origin

This is a copy

53% identical to SessionStart — 29 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 · 34 lines

What it actually says

{
  "SubagentStart": [
    {
      "matcher": "Explore",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/subagent-context.mjs\" explore",
          "timeout": 5
        }
      ]
    },
    {
      "matcher": "Plan",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/subagent-context.mjs\" plan",
          "timeout": 5
        }
      ]
    },
    {
      "matcher": "general-purpose",
      "hooks": [
        {
          "type": "command",
          "command": "node \"${CLAUDE_PLUGIN_ROOT}/scripts/subagent-context.mjs\" general",
          "timeout": 5
        }
      ]
    }
  ]
}
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 · 34 lines scan A 1461d2e9211a

Subscribe to this mod's changes

SubagentStart is a hook published in the GitHub repository hellowind777/hello2cc (695 stars, last pushed 3mo ago), licensed Apache-2.0. 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 53% identical to SessionStart, differing in 29 lines, and is treated as a copy.