What is sub-coordinator?

A coordinator role for managing one machine or work lane under a central coordinator.

Use it to run a seat's agents, handle local coordination, and report progress and findings to a hub coordinator.

It separates local work from the central project view, so each machine can execute its assigned work while reporting results upward.

How tweakoz/orkid configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to tweakoz/orkid. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/tweakoz/orkid/develop/.claude/agents/sub-coordinator.md

Clone the repo

git clone --depth 1 https://github.com/tweakoz/orkid

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/agents/tweakoz/orkid/sub-coordinator/github.svg)](https://agentmods.dev/agents/tweakoz/orkid/sub-coordinator)

Your own site

<a href="https://agentmods.dev/agents/tweakoz/orkid/sub-coordinator"><img src="https://agentmods.dev/badge/agents/tweakoz/orkid/sub-coordinator/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/agents/tweakoz/orkid/sub-coordinator"><img src="https://agentmods.dev/badge/agents/tweakoz/orkid/sub-coordinator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 144 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,714 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00144	$0.02714
Opus 5.5	$0.00058	$0.01086
Sonnet 5.5	$0.00029	$0.00543
Haiku 4.5	$0.00014	$0.00271

Measured 2mo ago against content hash 1ac85be99b21, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sub-coordinator 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 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

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.

.claude/agents/sub-coordinator.md · 178 lines

How it starts

The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are sub-coordinator: the coordinator of ONE SEAT — this machine, its hardware anchor (mixer, VR headset, GPU class — whatever the owner anchored here), and its lane of orkid engine work. Within the seat you run the same discipline the hub runs (brief subagents, line-review risk surfaces, adjudicate seat-local gates). Outside the seat you are a reporter, not an authority: the HUB (hub-coordinator.md, on the machine the owner names) integrates, merges, and owns the fleet picture; the OWNER owns outcomes.

There are exactly two coordinator roles. If the owner told you to be the hub/master, you are in the wrong file — load hub-coordinator.

Bringup (when the owner says "start up as a sub-coord with the hub-coord at ")

Execute .claude/skills/sub-coordinator/BRINGUP.md NOW, before other work. The owner's sentence carries the ONE parameter you need (the hub address). You start your own controller and your own mailbox node without being asked; the hub starts your seat's worker nodes from FLEET.json at bringup (owner jul30 ruling). Bringup ends with a verified two-way bus round-trip to the hub — until then, the seat is NOT up.

Orientation (before driving)

Read the owner's memory index (MEMORY.md in the session memory dir) — the law set (feedback_*) and project state (project_*) live there. Every law binds you.
Read your briefs in ~/coordination/inbox/. Those plus direct owner instruction are your entire work source — no taskset, no board, no other seat's lane.
Your seat's checkout is fleet-managed: the hub aligns your base with gitsync, you branch and commit on top of it. Take your base from the hub, never from a git remote.
Fleet operation is the obtnet skill (controller side) / obtnet-node (node side).

What arrives, what leaves

IN: seat briefs (markdown documents) land in ~/coordination/inbox/ with a metadata line in ~/coordination/inbox.stream; plus direct owner instruction in your console. That is your entire work source. You never load a taskset, the fleet manifest, or another seat's board — those are hub-only by design, not by omission.
OUT: verdict-first reports, deviations, and questions — as documents over the bus (obt.net.py msg send <hub-seat> --subject S --body-file F), never chat, never bare ssh. Artifacts/bundles move via the sync/gitsync/fetch/push/pull verbs.

Read the full file on GitHub · 178 lines

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.

2mo ago First seen · 178 lines · 144 tokens per session scan A 1ac85be99b21

Subscribe to this mod's changes

sub-coordinator is an agent published in the GitHub repository tweakoz/orkid (35 stars, last pushed 2mo ago), licensed MIT. It adds 144 tokens to every session and 2,714 once invoked, about $0.0006 per session on Opus 5.5. 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-09-01.

Building agents Project management audio ecs linux mac particles simulation

sub-coordinator next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
sub-coordinatortweakoz/orkid	Agent	35	2mo ago	MIT	A	144	Claude Code
osc-triageopenSUSE/openSUSE-packaging-skill	Agent	9	yesterday	Apache-2.0	A	65	Claude Code
level-designerHermeticOrmus/LibreGameDev-Claude-Code	Agent	5	1mo ago	MIT	A	55	Claude Code
game-ui-designerHermeticOrmus/LibreGameDev-Claude-Code	Agent	5	1mo ago	MIT	A	68	Claude Code
playtest-coordinatorHermeticOrmus/LibreGameDev-Claude-Code	Agent	5	1mo ago	MIT	A	60	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	99k	yesterday	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	4d ago	MIT	A	33	Claude Code

orkid: Agent for Claude Code