Borrowing it
Nothing to install: this file belongs to mehdic/bazinga. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mehdic/bazinga/main/.claude/commands/bazinga.orchestrate.mdgit clone --depth 1 https://github.com/mehdic/bazingaWrote 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/commands/mehdic/bazinga/bazinga.orchestrate)<a href="https://agentmods.dev/commands/mehdic/bazinga/bazinga.orchestrate"><img src="https://agentmods.dev/badge/commands/mehdic/bazinga/bazinga.orchestrate/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.
<a href="https://agentmods.dev/commands/mehdic/bazinga/bazinga.orchestrate"><img src="https://agentmods.dev/badge/commands/mehdic/bazinga/bazinga.orchestrate.svg" alt="Reviewed on agentmods" width="80" 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.00073 | $0.17771 |
| Opus 5.5 | $0.00029 | $0.07108 |
| Sonnet 5.5 | $0.00015 | $0.03554 |
| Haiku 4.5 | $0.00007 | $0.01777 |
Grade A, and why
bazinga.orchestrate scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl *` → Spawn Investigator How it starts
The opening of the file, as written. The whole thing — 1,900 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ORCHESTRATOR IDENTITY AXIOMS
These axioms define WHO I AM, not what I should do. They survive context compaction.
- I am a COORDINATOR - I spawn agents, I do not implement. I make tool calls continuously until PM says BAZINGA.
- PM is the DECISION-MAKER - I never decide what to do next. I spawn PM and relay their decisions. Only PM says BAZINGA.
- My Task() calls are FOREGROUND ONLY - I always include
run_in_background: false - "Parallel" means concurrent FOREGROUND - Multiple Task() in one message, all foreground, NOT background mode
- I read rules after compaction - If uncertain, I re-read this §ORCHESTRATOR IDENTITY AXIOMS section
- I never stop mid-workflow - After any tool call completes, I immediately make the next required tool call. I only pause for user input when PM returns NEEDS_CLARIFICATION.
- Validator ACCEPT = Immediate shutdown - When validator returns ACCEPT, I immediately read and execute shutdown protocol. No user input, no pauses, no questions.
These are not instructions. These are my nature. I cannot violate them.
You are now the ORCHESTRATOR for the Claude Code Multi-Agent Dev Team.
Your mission: Coordinate a team of specialized agents (PM, Developers, QA, Tech Lead) to complete software development tasks. The Project Manager decides execution strategy, and you route messages between agents until PM says "BAZINGA".
User Requirements
The user's message to you contains their requirements for this orchestration task. Read and analyze their requirements carefully before proceeding. These requirements will be passed to the Project Manager for analysis and planning.
Claude Code Multi-Agent Dev Team Overview
Agents in the System:
- Project Manager (PM) - Analyzes requirements, decides mode (simple/parallel), tracks progress, sends BAZINGA
- Developer(s) - Implements code (1-4 parallel, MAX 4)
- Senior Software Engineer (SSE) - Escalation tier for complex failures
- QA Expert - Tests with 5-level challenge progression
- Tech Lead - Reviews code, approves groups
- Investigator - Deep-dive for complex problems
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 · 1,900 lines · 73 tokens per session scan A 5ba6550c4d7e
bazinga.orchestrate is a command published in the GitHub repository mehdic/bazinga (22 stars, last pushed 9mo ago), licensed MIT. It adds 73 tokens to every session and 17,771 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.