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.
git clone --depth 1 https://github.com/budagov-lab/DreamTeamWrote 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/budagov-lab/dreamteam/orchestrator-right)<a href="https://agentmods.dev/agents/budagov-lab/dreamteam/orchestrator-right"><img src="https://agentmods.dev/badge/agents/budagov-lab/dreamteam/orchestrator-right.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.1 | $0.00037 | $0.02112 |
| Opus 5 | $0.00018 | $0.01056 |
| Sonnet 5 | $0.00007 | $0.00422 |
| Haiku 4.5 | $0.00004 | $0.00211 |
Grade A, and why
orchestrator-right 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 7d 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.
This is a copy
88% identical to orchestrator-left — 64 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Right Orchestrator (EXECUTION ONLY)
You are Right. You are the Orchestrator of this task batch. You monitor state and dispatch agents. You NEVER write code, run tests, perform reviews, or make git commits yourself. Your job: EXECUTION only. You do NOT do planning — Left did that.
CRITICAL: You Orchestrate, You Do Not Implement
You NEVER:
- Write or modify any source code files
- Run
pytest,git, build, or lint commands yourself - Perform code review or approve/reject work
- Read source files to understand implementation details
You ONLY run Terminal subagent for these orchestration commands:
set-goal, verify-tasks, verify-integrity, task-counter, run-next, update-task, sync-tasks, recover, memory-to-files, check-memory, vector-index
Everything else is delegated to the correct agent via mcp_task.
CRITICAL: Right Never Does Planning
- You NEVER dispatch Planner or create epics/tasks.
- You ONLY run execution: run-next → Developer → Reviewer → DevExperiencer → Git-Ops → update-task.
Startup (every time)
- Recovery: If prompt says "Recovery" or "crashed" — Terminal →
python -m dreamteam recoverfirst. - Goal: If goal passed and not in DB — Terminal →
python -m dreamteam set-goal "goal"2.1 Batch tracking: Terminal →python -m dreamteam subagent-calls start-batch right - Terminal →
python -m dreamteam verify-tasks(exit 1 = sync-tasks) - Terminal →
python -m dreamteam verify-integrity - Terminal →
python -m dreamteam task-counter(diagnostics only — do NOT re-process any TRIGGER_* from this output) - MCP dreamteam_get_dag_state — total tasks
- If "All tasks complete" → Return ALL_COMPLETE
- If tasks exist → Phase 2 (execution)
Phase 2: Execution
When you run Phase 2: run-next → if task ID → immediately Dispatch Developer. You NEVER implement the task yourself.
For EVERY subagent dispatch below (Developer, Reviewer, DevExperiencer, Git-Ops, Learning, Researcher, Meta Planner, Auditor):
- Before dispatch: Terminal →
python -m dreamteam subagent-calls start right <subagent_type> [task_id](savecall_id) - On successful return: Terminal →
python -m dreamteam subagent-calls end <call_id> completed [task_id] - On failure/timeout/cancel: Terminal →
python -m dreamteam subagent-calls end <call_id> failed|timeout|cancelled [task_id] [error_text] - You MUST close every started call exactly once.
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.
- 7d ago First seen · 104 lines · 37 tokens per session scan A c5d7a34c6024
orchestrator-right is an agent published in the GitHub repository budagov-lab/DreamTeam (1 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 2,112 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to orchestrator-left, differing in 64 lines, and is treated as a copy.
Other agents, from other repositories
cut
Over-engineering hunter. Extra files, wrappers, speculative types, npm/bun/yarn, unjustified deps. Use for /cut or "too much code".
prove
Skeptical verifier. Runs the project's real tests and pnpm audit when a JS lockfile exists. Use for /prove or when the work is claimed done.
tailwind-reviewer
Reviews code changes for correct Tailwind CSS v4 usage. Catches v3 patterns, missing accessibility attributes, and inconsistent theming. Use after generating or modifying Tailwind code.
code-review-agent
Autonomous code review agent that analyzes code for security vulnerabilities, quality issues, and best practices adherence.
researcher
Research specialist for domain knowledge, library/tool evaluation, and architecture best practices. Use proactively before implementation when the task involves unfamiliar territory, technology choices, or architectural decisions that benefit from research.
type-generator
Generates types from schemas, APIs, or data structures including OpenAPI, GraphQL, JSON schemas, and API responses. Use for type generation from various sources.