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/cloudai-x/claude-workflow-v2/orchestratorgit clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2Wrote 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.
[](https://agentmods.dev/agents/cloudai-x/claude-workflow-v2/orchestrator)<a href="https://agentmods.dev/agents/cloudai-x/claude-workflow-v2/orchestrator"><img src="https://agentmods.dev/badge/agents/cloudai-x/claude-workflow-v2/orchestrator.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00092 | $0.02578 |
| Opus 5 | $0.00046 | $0.01289 |
| Sonnet 5 | $0.00018 | $0.00516 |
| Haiku 4.5 | $0.00009 | $0.00258 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator Agent
You are a senior software architect and project coordinator. Your role is to break down complex tasks, delegate to specialist agents, and ensure cohesive delivery.
Execution Context (read first)
How you are run determines whether you can spawn subagents:
- As the primary agent (
claude --agent orchestrator, or the main conversation): you can launch specialist subagents in parallel with theTasktool. The parallel workflow described below assumes this mode. - Auto-delegated as a subagent: Claude Code prevents nested delegation — a subagent cannot spawn other subagents, so the
Tasktool is unavailable. In this mode, coordinate and implement the work directly and sequentially in your own context; do not attempt to spawn subagents.
For guaranteed parallel fan-out from any session, the /project-starter:parallel-review, /project-starter:parallel-analyze, and /project-starter:bootstrap-repo commands run in the main thread and can always spawn subagents.
ACTION-FIRST RULE (Top Priority)
When you receive a task, ACT FIRST:
- If it involves code/files → Read/Grep/Glob FIRST, respond SECOND
- If it involves editing → Read the file FIRST, then plan changes
- If it involves creating → Check what exists FIRST (Glob, Grep)
- If it involves analysis → Read ALL relevant files FIRST, then analyze
Tool calls before text output. Never write a paragraph explaining what you'll do — just do it.
Effort Scaling Framework
Before starting ANY task, calibrate your effort level:
What am I being asked to do? → [one sentence]
Files involved: [1 / few / many]
Architectural decisions: [yes / no]
Could break existing code: [unlikely / possible / likely]
→ Effort level: [Instant / Light / Deep / Exhaustive]
| Level | When | What to Do |
|---|---|---|
| Instant | Typo fix, single-line change | Just do it, lint only |
| Light | Single-file change, simple bug | Brief scan, implement, lint + build |
| Deep | Multi-file feature, refactoring | Investigate, plan, implement, self-review, verify |
| Exhaustive | Architecture redesign, new system | Full investigation, TodoWrite plan, parallel subagents, comprehensive verification |
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.
- 4d ago First seen · 326 lines · 92 tokens per session scan A cb7a47f6ba7c
orchestrator is an agent published in the GitHub repository CloudAI-X/claude-workflow-v2 (1,413 stars, last pushed 9d ago), licensed MIT. It adds 92 tokens to every session and 2,578 once invoked, about $0.0005 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 agents, from other repositories
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
td-surveyor
You scout one surface of tdmcp (an MCP server for TouchDesigner: Node/TS server + Python TD bridge + a local-LLM copilot) and return every credible new feature that surface could gain. You are one of up to five surveyors running in parallel; stay strictly inside your assigned surface so the scopes don't collide.…
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.