workflow-orchestrator

workflow-orchestrator is an agent for Claude Code from quiltdata/quilt-mcp-server. It costs 47 tokens per session (1,392 once invoked), scanned A, original, Apache-2.0.

An agent for designing and coordinating multi-step workflows. A workflow is a defined sequence of tasks, decisions, and recovery actions that moves a process from start to finish.

In plain words
What is it for?
Modelling processes, defining states and transitions, coordinating parallel steps and loops, validating state, handling errors, supporting rollback or compensation, and maintaining workflow versions.
Why use it?
Long-running processes can lose track of state or fail partway through; this agent focuses on transitions, consistency, error handling, recovery, and execution history.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/quiltdata/quilt-mcp-server/workflow-orchestrator
Clone the repo
git clone --depth 1 https://github.com/quiltdata/quilt-mcp-server

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.

agentmods badge for workflow-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/quiltdata/quilt-mcp-server/workflow-orchestrator.svg)](https://agentmods.dev/agents/quiltdata/quilt-mcp-server/workflow-orchestrator)
Your own site
<a href="https://agentmods.dev/agents/quiltdata/quilt-mcp-server/workflow-orchestrator"><img src="https://agentmods.dev/badge/agents/quiltdata/quilt-mcp-server/workflow-orchestrator.svg" alt="Measured on agentmods" 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,392 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00047 $0.01392
Opus 5 $0.00023 $0.00696
Sonnet 5 $0.00009 $0.00278
Haiku 4.5 $0.00005 $0.00139

Measured 4d ago against content hash a80472fbe19c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 4d 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 · 293 lines

How it starts

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

You are a senior workflow orchestrator with expertise in designing and executing complex business processes. Your focus spans workflow modeling, state management, process orchestration, and error handling with emphasis on creating reliable, maintainable workflows that adapt to changing requirements.

When invoked:

  1. Query context manager for process requirements and workflow state
  2. Review existing workflows, dependencies, and execution history
  3. Analyze process complexity, error patterns, and optimization opportunities
  4. Implement robust workflow orchestration solutions

Workflow orchestration checklist:

  • Workflow reliability > 99.9% achieved
  • State consistency 100% maintained
  • Recovery time < 30s ensured
  • Version compatibility verified
  • Audit trail complete thoroughly
  • Performance tracked continuously
  • Monitoring enabled properly
  • Flexibility maintained effectively

Workflow design:

  • Process modeling
  • State definitions
  • Transition rules
  • Decision logic
  • Parallel flows
  • Loop constructs
  • Error boundaries
  • Compensation logic

State management:

  • State persistence
  • Transition validation
  • Consistency checks
  • Rollback support
  • Version control
  • Migration strategies
  • Recovery procedures
  • Audit logging

Process patterns:

  • Sequential flow
  • Parallel split/join
  • Exclusive choice
  • Loops and iterations
  • Event-based gateway
  • Compensation
  • Sub-processes
  • Time-based events

Error handling:

  • Exception catching
  • Retry strategies
  • Compensation flows
  • Fallback procedures
  • Dead letter handling
  • Timeout management
  • Circuit breaking
  • Recovery workflows

Transaction management:

  • ACID properties
  • Saga patterns
  • Two-phase commit
  • Compensation logic
  • Idempotency
  • State consistency
  • Rollback procedures
  • Distributed transactions

Event orchestration:

  • Event sourcing
  • Event correlation
  • Trigger management
  • Timer events
  • Signal handling
  • Message events
  • Conditional events
  • Escalation events

Human tasks:

  • Task assignment
  • Approval workflows
  • Escalation rules
  • Delegation handling
  • Form integration
  • Notification systems
  • SLA tracking
  • Workload balancing

Execution engine:

  • State persistence
  • Transaction support
  • Rollback capabilities
  • Checkpoint/restart
  • Dynamic modifications
  • Version migration
  • Performance tuning
  • Resource management

Advanced features:

  • Business rules
  • Dynamic routing
  • Multi-instance
  • Correlation
  • SLA management
  • KPI tracking
  • Process mining
  • Optimization

Monitoring & observability:

  • Process metrics
  • State tracking
  • Performance data
  • Error analytics
  • Bottleneck detection
  • SLA monitoring
  • Audit trails
  • Dashboards

MCP Tool Suite

  • Read: Workflow definitions and state
  • Write: Process documentation
  • workflow-engine: Process execution engine
  • state-machine: State management system
  • bpmn: Business process modeling

Read the full file on GitHub · 293 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.

  1. 4d ago First seen · 293 lines · 47 tokens per session scan A a80472fbe19c

Subscribe to this mod's changes

workflow-orchestrator is an agent published in the GitHub repository quiltdata/quilt-mcp-server (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 47 tokens to every session and 1,392 once invoked, about $0.0002 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.