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 skills add Everyone-Needs-A-Copilot/claude-copilot --skill orchestrategit clone --depth 1 https://github.com/Everyone-Needs-A-Copilot/claude-copilotWrote 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.
[](https://agentmods.dev/skills/everyone-needs-a-copilot/claude-copilot/orchestrate)<a href="https://agentmods.dev/skills/everyone-needs-a-copilot/claude-copilot/orchestrate"><img src="https://agentmods.dev/badge/skills/everyone-needs-a-copilot/claude-copilot/orchestrate/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.
<a href="https://agentmods.dev/skills/everyone-needs-a-copilot/claude-copilot/orchestrate"><img src="https://agentmods.dev/badge/skills/everyone-needs-a-copilot/claude-copilot/orchestrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.00465 |
| Opus 5.5 | $0.00017 | $0.00186 |
| Sonnet 5.5 | $0.00008 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
orchestrate 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 6d 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.
What it actually says
Orchestrate
Coordinate parallel work in a Codex-native way.
Boundary
Codex Copilot does not auto-spawn workers unless the user explicitly asks for delegation or parallel execution.
Workflow
- Use
tato create a PRD, task breakdown, streams, dependencies, and file ownership. - Validate stream dependencies and file overlap with
scripts/orchestrate-validate.pybefore any parallel work begins. - Use git worktrees only after confirming the branch/worktree plan with the user.
- Spawn Codex subagents only when explicitly requested.
- Keep write scopes disjoint and route each implementation stream through
qa. - Treat merge, cleanup, and removal operations as separate actions requiring explicit current approval when destructive.
- For a user-requested cost-capped non-interactive worker, pass
--max-budget-usdthroughtc worker; do not imply that stored metadata enforces a cap unless the installedtccontract says so.
Stream Metadata
Each stream should declare:
{
"streamId": "Stream-A",
"streamName": "Foundation",
"files": ["src/example.ts"],
"streamDependencies": [],
"streamPaths": ["src/example/**"],
"streamTokenBudget": 2500
}
Launch Template
When the user explicitly approves delegation, spawn each stream with:
- specialist role and skill
- task id and stream id
- owned files or path globs
- forbidden paths
- expected work product and QA route
Output
- stream plan
- dependency graph
- file ownership map
- launch instructions or local execution plan
Work Lifecycle
Apply the shared work lifecycle once per task, including direct invocation of this skill: start/resume, maintain, pause/handoff, finish and later reuse. Keep the checkpoint proportional in the existing record; a small answer does not need a new task or document.
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.
- 6d ago Changed 03eada0de306
- 7d ago Changed · +7 lines 505025f51e16
- 1mo ago First seen · 57 lines · 42 tokens per session scan A 8c26c9ae6408
orchestrate is a skill published in the GitHub repository Everyone-Needs-A-Copilot/claude-copilot (14 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 465 once invoked, about $0.0002 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-04.
Other skills, from other repositories
theokit-agents
TheoKit agent/LLM integration — agents/.ts convention (AgentBuilder), the tool() builder, capabilities (advanced/DI), useAgent client hook.
theokit-ui
@theokit/ui AI-native component library — AI-agent surfaces (ChatThread, ChatMessage, ChatComposer, ToolCallCard, AgentStream), theming, providers; generic primitives (CodeBlock, Sidebar, Button) come from @usetheo/ui.
theokit-gateways
Receiving messages from Telegram, WhatsApp, Slack and other platforms — handleChannelWebhook, the @theokit/gateway- adapters, signature validation, the onMessage seam.
theokit-frontend
TheoKit frontend — file-based routing, layouts, theoFetch typed client, useAgent, React patterns.
theokit-routes
TheoKit server routes — the route() builder, Zod validation, HTTP methods, dynamic params, error handling.
theokit-config
TheoKit configuration — the config() builder, plugins, security, storage, agents, build targets.