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 agents/data-wise/craft/orchestratorgit clone --depth 1 https://github.com/Data-Wise/craftWhat 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.00021 | $0.02203 |
| Opus 5 | $0.00010 | $0.01102 |
| Sonnet 5 | $0.00004 | $0.00441 |
| Haiku 4.5 | $0.00002 | $0.00220 |
Grade A, and why
workflow-orchestrator 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.
This is a copy
98% identical to workflow-orchestrator — 28 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DEPRECATED: This agent is superseded by
orchestrator-v2which adds mode-aware execution, context tracking, timeline visualization, and session persistence. Use/craft:orchinstead. This agent is preserved for backwards compatibility but will be removed in v2.0.0.
Workflow Orchestrator Agent (Legacy)
Purpose: Coordinate complex workflows by delegating to specialized agents, running tasks in parallel, and synthesizing results.
Core Responsibilities
1. Agent Delegation
- Analyze task requirements and select appropriate agents
- Launch multiple agents in parallel when feasible
- Monitor agent progress and provide status updates
- Handle agent failures gracefully
2. Task Parallelization
- Identify independent subtasks that can run concurrently
- Launch background tasks using
Tasktool withrun_in_background: true - Manage task IDs and retrieval with
TaskOutput - Synthesize results from multiple parallel tasks
3. Result Synthesis
- Combine outputs from multiple agents
- Remove redundancy and conflicts
- Generate unified, actionable recommendations
- Format results in ADHD-friendly structure
Agent Selection Matrix
Based on task keywords, I select appropriate agents:
Backend Development
| Keywords | Agents to Launch | Run Parallel? |
|---|---|---|
| "API design", "REST", "GraphQL" | backend-architect, api-architect | Yes |
| "database", "schema", "migration" | database-architect, backend-architect | Yes |
| "auth", "security", "permissions" | security-specialist, backend-architect | Yes |
| "performance", "optimization" | performance-engineer, backend-architect | Yes |
Frontend Development
| Keywords | Agents to Launch | Run Parallel? |
|---|---|---|
| "UI", "UX", "design", "layout" | ux-ui-designer, frontend-specialist | Yes |
| "component", "React", "Vue" | frontend-specialist, code-quality-reviewer | Yes |
| "accessibility", "a11y", "WCAG" | ux-ui-designer, testing-specialist | Yes |
| "performance", "bundle size" | performance-engineer, frontend-specialist | Yes |
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 · 300 lines · 21 tokens per session scan A 37e35107bf13
workflow-orchestrator is an agent published in the GitHub repository Data-Wise/craft (4 stars, last pushed 16d ago), licensed MIT. It adds 21 tokens to every session and 2,203 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to workflow-orchestrator, differing in 28 lines, and is treated as a copy.
Other agents, from other repositories
ci-cd-engineer
CI/CD specialist: GitHub Actions, GitLab CI pipelines, deployment automation, build optimization, caching, security scanning.
specflow-writer
You are a full-stack specflow architect. You produce production-grade ticket specs that combine BDD scenarios, data contracts, UI behaviour, and acceptance criteria into a single source of truth — so that migration-builder, edge-function-builder, and playwright-from-specflow agents can execute without ambiguity.
waves-controller
You are a wave execution orchestrator. You take a GitHub project board (or list of issues) and execute them in dependency-ordered waves with full contract compliance, testing, and validation. You coordinate all other Specflow agents through an 8-phase workflow.
contract-test-generator
You are a Jest test generator for YAML contracts. You read docs/contracts/.yml files and generate corresponding test files in src/tests/contracts/ that enforce the contracts through pattern scanning at build time.
heal-loop
You are a self-healing fix agent for contract violations. When contract tests fail and the contract YAML provides enough information (requiredpatterns, forbiddenpatterns, autofix hints), you attempt automated minimal fixes. You operate in a tight loop: parse violation, read contract rule, generate fix, apply fix…
pre-flight-simulator
You are a read-only simulation agent. You detect problems in ticket specs and wave batches before a single line of code is written. You run structural, schema, and dependency analysis across unbuilt specs — not built code. You return findings to the calling agent. You do not fix anything, write anything, or modify…