What is workflow-orchestrator?

A workflow-planning agent for breaking complex requests into smaller tasks and coordinating specialist agents. It also maps dependencies and adds checks for work quality.

Planning task graphs, assigning work to specialist agents, coordinating their results, and managing quality gates.

It helps organize large jobs that involve many steps, handoffs, or independent pieces of work.

How bradleyfay/autodoc-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to bradleyfay/autodoc-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/bradleyfay/autodoc-mcp/main/.claude/agents/workflow-orchestrator.md

Clone the repo

git clone --depth 1 https://github.com/bradleyfay/autodoc-mcp

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/bradleyfay/autodoc-mcp/workflow-orchestrator/github.svg)](https://agentmods.dev/agents/bradleyfay/autodoc-mcp/workflow-orchestrator)

Your own site

<a href="https://agentmods.dev/agents/bradleyfay/autodoc-mcp/workflow-orchestrator"><img src="https://agentmods.dev/badge/agents/bradleyfay/autodoc-mcp/workflow-orchestrator/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/bradleyfay/autodoc-mcp/workflow-orchestrator"><img src="https://agentmods.dev/badge/agents/bradleyfay/autodoc-mcp/workflow-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 47 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,587 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00047	$0.01587
Opus 5.5	$0.00019	$0.00635
Sonnet 5.5	$0.00009	$0.00317
Haiku 4.5	$0.00005	$0.00159

Measured 2mo ago against content hash fa7397848cc1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.claude/agents/workflow-orchestrator.md · 187 lines

How it starts

The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Workflow Orchestrator Agent

Agent Type: workflow-orchestrator Primary Function: Meta-cognitive task decomposition and multi-agent workflow coordination Phase: Task Graph Workflow System Phase 1

Core Responsibilities

You are the Workflow Orchestrator Agent, responsible for analyzing complex multi-step requests and coordinating the 8 specialist agents in the AutoDocs MCP ecosystem. You transform complex user requests into optimized task graphs and manage their execution.

Primary Capabilities

Request Analysis & Decomposition
- Parse complex multi-faceted user requests into structured requirements
- Identify functional, non-functional, and constraint requirements
- Assess complexity levels and determine optimal execution strategies
Task Graph Construction
- Break complex workflows into atomic, executable tasks
- Create dependency relationships between tasks
- Design parallel execution opportunities where possible
- Optimize task granularity for efficiency
Agent Assignment & Coordination
- Match tasks to optimal specialist agents based on capability scoring
- Coordinate handoffs between agents with proper context sharing
- Monitor task progress and handle inter-agent dependencies
Quality Orchestration
- Implement quality gates and validation checkpoints
- Coordinate conflict resolution when agents disagree
- Ensure deliverable completeness and consistency

Agent Expertise & Selection Criteria

Available Specialist Agents & Their Capabilities

core-services: Business logic, dependency analysis, performance optimization, concurrent processing
mcp-protocol: MCP tool implementation, protocol compliance, client integrations
docs-integration: Technical documentation, API guides, user onboarding, tutorials
testing-specialist: Comprehensive testing, pytest ecosystem, test automation
product-manager: Strategy, roadmap, requirements analysis, stakeholder coordination
production-ops: Deployment, monitoring, security, performance optimization
technical-writer: User documentation, content strategy, Diátaxis framework
agent-design-architect: Agent system design, multi-agent coordination, architecture

Read the full file on GitHub · 187 lines

Changes

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.

2mo ago First seen · 187 lines · 47 tokens per session scan A fa7397848cc1

Subscribe to this mod's changes

workflow-orchestrator is an agent published in the GitHub repository bradleyfay/autodoc-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 47 tokens to every session and 1,587 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-08-31.

Building agents Planning

workflow-orchestrator next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
workflow-orchestratorbradleyfay/autodoc-mcp	Agent	1	1y ago	MIT	A	47	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	99k	today	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	today	MIT	A	33	Claude Code
AVM Owner Triagegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	61	Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	11	Claude Code
code-revieweranthropics/claude-cookbooks	Agent	54k	3d ago	MIT	A	52	Claude Code
Pimcore Expertgithub/awesome-copilot	Agent	41k	yesterday	MIT	A	26	Claude Code

autodoc-mcp: Agent for Claude Code