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.
npx agentmods add skills/tweakoz/orkid/sub-coordinatornpx skills add tweakoz/orkid --skill sub-coordinatorgit clone --depth 1 https://github.com/tweakoz/orkidWhat 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 | $0.00107 | $0.00338 |
| Opus 5 | $0.00053 | $0.00169 |
| Sonnet 5 | $0.00021 | $0.00068 |
| Haiku 4.5 | $0.00011 | $0.00034 |
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 yesterday.
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.
What it actually says
sub-coordinator — a seat under the hub
Two files, in this order, both mandatory:
.claude/agents/sub-coordinator.md— Read IN FULL. The canonical role: what arrives (briefs) and leaves (reports), the reply-path law, the yours/not-yours boundary.BRINGUP.md(this folder) — if the owner's instruction was to start up, EXECUTE it now with the hub address from the owner's sentence: own controller + mailbox node start without asking; ends with a verified two-way round-trip to the hub. Worker nodes stay owner-started.
Wrong role? If this session was told to be the hub/master/integration seat, load
hub-coordinator instead — this skill is for a seat working UNDER one.
Bus/routing reference: .claude/skills/hub-coordinator/COORDINATION_OPS.md.
Fleet operation: the obtnet skill (controller side) and obtnet-node (node side).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 23 lines · 107 tokens per session scan A f68183ad85f9
sub-coordinator is a skill published in the GitHub repository tweakoz/orkid (35 stars, last pushed 21d ago), licensed MIT. It adds 107 tokens to every session and 338 once invoked, about $0.0005 per session on Opus 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.
Other skills, from other repositories
host-pattern
Use when adding a new domain to Nuclear's plugin system, or implementing a host. Covers the host pattern (how player functionality is exposed to plugins), the host interface and API class structure, how hosts are implemented in the player, error handling conventions, and what files to create and modify. Trigger…
creating-components
Use when creating new UI components in packages/ui. Covers component structure, tests, stories, and what to avoid.
writing-docs
Use when writing or editing documentation in packages/docs. Covers Gitbook markdown syntax, special blocks, page structure, and the SUMMARY.md table of contents. Trigger phrases include "write docs", "add documentation", "docs page", "gitbook", "user manual".
writing-plugins
Use when writing, scaffolding, or modifying Nuclear plugins. Covers plugin structure, manifest, entry point, provider types, available APIs, and publishing. Trigger phrases include "create a plugin", "write a plugin", "plugin scaffold", "streaming provider", "metadata provider".
analyzing-linux-kernel-rootkits
Detect kernel-level rootkits in Linux memory dumps using Volatility3 linux plugins (checksyscall, lsmod, hiddenmodules), rkhunter system scanning, and /proc vs /sys discrepancy analysis to identify hooked syscalls, hidden kernel modules, and tampered system structures.
triage-issue-local
Repo-specific triage guidance for warp. Only the categories declared overridable by the core triage-issue skill may be specialized here.