subagent

What it does

Orchestrators reading for context: this is the protocol your dispatched subagents follow. You don't act on it yourself -- write briefs that satisfy the four required fields described below, and rely on each spawned subagent to drive the loop on its end. Stop reading at "Host conventions" if you only need the brief shape; the rest is for the subagent.

What it can touch

• No script files in its folder

  Its folder holds text, not programs — but the instructions do tell your AI to run commands (see below).

  How we know

  Listed the one file in the skill’s folder on GitHub; none is a script or program.

• Uses terminal commands

  It shows your AI commands to run. In a coding agent that means your terminal; in a chat app it usually can’t.

  How we know

  The SKILL.md contains shell code blocks.

• No known risk pattern found

  Launch7’s automated check read all 1 text files in this skill and matched none of its risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.

  How we know

  Read 2026-10-05, commit ab5fbd6 by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.

• Recently maintained

  Its repository has had changes recently.

  How we know

  Last push to evo-hq/evo: 2026-07-17 (80 days before the scan).

Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check

Add it to your AI