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/treex-x/workflowx/orchestratexnpx skills add TreeX-X/WorkFlowX --skill orchestratexgit clone --depth 1 https://github.com/TreeX-X/WorkFlowXWhat 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.00022 | $0.00688 |
| Opus 5 | $0.00011 | $0.00344 |
| Sonnet 5 | $0.00004 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
orchestrateX 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 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
orchestrateX
Routing
Read the complete request and active context before selecting a mode.
- Explicit
xdo,xdel,xflow, orxstatuscommands take precedence. - Without an explicit mode, recommend
xflowfor high-impact, cross-module, or uncertain work; recommendxdelfor clear local work with an existing or requested Hybrid Tree; otherwise recommendxdo. - When the mode is ambiguous, present the three choices instead of silently selecting one.
- Once a mode is active, keep subsequent messages in that mode until completion.
- Parallel development is never implicit; activate it only when the user explicitly requests parallel work.
Modes
xdo - direct
- Main Agent works directly using the requested skills.
- Do not dispatch by default.
- Parallel Agents are allowed only when the user explicitly requests parallel development.
- Hybrid Tree and harness are optional.
- Use
engineeringXand perform self-review before reporting completion.
xdel - delegate
- Use or create a Hybrid Tree Parent/Child.
- Dispatch coderX once for the assigned Child.
- coderX reads
engineeringXandspecX, then self-reviews. - Do not trigger evaluatorX or an iteration loop.
xflow - orchestrate
- Run module 08 repository discovery, then load and run
.claude/skills/socratesX/SKILL.mdfor only the unresolved decisions in the current analysis phase. Ask those questions in one batch, offer options only for real trade-offs, and use one confirmed Ready Summary gate before creating or updating the Hybrid Tree. - Execute Children in dependency order.
- Dispatch coderX once per Child with
engineeringXandspecX. - Trigger evaluatorX after each Child.
- After evaluation, the Main Agent classifies findings:
- local implementation defect: re-dispatch the same Child once with a minimal repair packet;
- cross-Child integration issue: compress it into an integration note for the affected later Child;
- architecture or scope issue: the Main Agent updates the plan or fixes it directly.
- A Child gets at most one automatic repair re-dispatch by default. Further repair requires a Main Agent decision.
- Do not pass complete prior Child context to later Children; pass only relevant contracts, files, failures, and risks.
What ships with it
6 files 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.
- 2d ago First seen · 61 lines · 22 tokens per session scan A 8b7c0a716c52
orchestrateX is a skill published in the GitHub repository TreeX-X/WorkFlowX (55 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 688 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
agent-orchestrator
Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management.
project-orchestration
Orchestrate multi-agent workflows for feature development using planning agents, context handoff, and stage management.
skill-creator
Generates Anthropic Skills with complete workflow including GitHub PR creation and local download verification.
Ability Generator
This skill generates markdown skill templates to be later used.
agent-orchestrator-v2
Agent Orchestrator workflow skill. Use this skill when the user needs Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management and the operator should preserve the upstream workflow, copied support files, and…
agent-team
Build low-context multi-agent teams with durable handoff, independent review, and user gates. Use when a project needs separate management, execution, and review roles.