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/claude-plugins/orchestratorgit clone --depth 1 https://github.com/Data-Wise/claude-pluginsWhat 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.02240 |
| Opus 5 | $0.00010 | $0.01120 |
| Sonnet 5 | $0.00004 | $0.00448 |
| Haiku 4.5 | $0.00002 | $0.00224 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- workflow-orchestrator — 98% identical, 28 lines differ
How it starts
The opening of the file, as written. The whole thing — 292 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:orchestrateinstead. 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 · 292 lines · 21 tokens per session scan A cf56d8b6c98c
workflow-orchestrator is an agent published in the GitHub repository Data-Wise/claude-plugins (7 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 2,240 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.