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 skills/bdiasti/maestro-bundle-cli/agent-orchestrationnpx skills add bdiasti/maestro-bundle-cli --skill agent-orchestrationgit clone --depth 1 https://github.com/bdiasti/maestro-bundle-cliWrote 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/skills/bdiasti/maestro-bundle-cli/agent-orchestration)<a href="https://agentmods.dev/skills/bdiasti/maestro-bundle-cli/agent-orchestration"><img src="https://agentmods.dev/badge/skills/bdiasti/maestro-bundle-cli/agent-orchestration.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.00040 | $0.01618 |
| Opus 5 | $0.00020 | $0.00809 |
| Sonnet 5 | $0.00008 | $0.00324 |
| Haiku 4.5 | $0.00004 | $0.00162 |
Grade A, and why
agent-orchestration 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 5d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Orchestration
Design and implement multi-agent systems where an orchestrator coordinates specialized subagents through task planning, intelligent routing, compliance validation, and human-in-the-loop approval.
When to Use
- Coordinating multiple specialized agents (frontend, backend, devops)
- Implementing task decomposition and delegation workflows
- Building a LangGraph StateGraph with routing logic
- Adding human-in-the-loop approval gates for destructive operations
- Creating agent pipelines that validate compliance before merging work
Available Operations
- Define orchestrator state schema
- Build the orchestrator graph with nodes and edges
- Implement intelligent task routing
- Delegate tasks to specialized subagents
- Add compliance validation nodes
- Wire up human-in-the-loop interrupt gates
- Merge work from multiple agent branches
Multi-Step Workflow
Step 1: Define the Orchestrator State
Create a typed state schema that tracks the full lifecycle of a demand.
from typing import TypedDict, Annotated, Literal
from langgraph.graph.message import add_messages
class OrchestratorState(TypedDict):
messages: Annotated[list, add_messages]
demand: dict
task_plan: list[dict]
current_task_index: int
assigned_agents: dict[str, str] # task_id -> agent_type
branch_status: dict[str, str] # agent -> branch_name
compliance_results: list[dict]
needs_human_review: bool
final_status: str
Step 2: Build the Graph Structure
Wire up the orchestrator nodes and conditional edges.
from langgraph.graph import StateGraph, START, END
from langgraph.checkpoint.postgres import PostgresSaver
graph = StateGraph(OrchestratorState)
# Add nodes
graph.add_node("analyze_demand", analyze_demand_node)
graph.add_node("plan_tasks", plan_tasks_node)
graph.add_node("route_to_agent", route_to_agent_node)
graph.add_node("execute_agent", execute_agent_node)
graph.add_node("validate_compliance", validate_compliance_node)
graph.add_node("human_review", human_review_node)
graph.add_node("merge_work", merge_work_node)
# Wire edges
graph.add_edge(START, "analyze_demand")
graph.add_edge("analyze_demand", "plan_tasks")
graph.add_edge("plan_tasks", "route_to_agent")
graph.add_conditional_edges("route_to_agent", should_continue, {
"execute": "execute_agent",
"all_done": "validate_compliance"
})
graph.add_edge("execute_agent", "route_to_agent")
graph.add_conditional_edges("validate_compliance", needs_review, {
"review": "human_review",
"pass": "merge_work"
})
graph.add_edge("human_review", "merge_work")
graph.add_edge("merge_work", END)
app = graph.compile(checkpointer=PostgresSaver(conn))
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 199 lines · 40 tokens per session scan A ebf369fd0dd7
agent-orchestration is a skill published in the GitHub repository bdiasti/maestro-bundle-cli (21 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 1,618 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…