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-advanced.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-advanced)<a href="https://agentmods.dev/commands/mehdic/bazinga/bazinga.orchestrate-advanced"><img src="https://agentmods.dev/badge/commands/mehdic/bazinga/bazinga.orchestrate-advanced.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.00029 | $0.01799 |
| Opus 5 | $0.00015 | $0.00899 |
| Sonnet 5 | $0.00006 | $0.00360 |
| Haiku 4.5 | $0.00003 | $0.00180 |
Grade A, and why
bazinga.orchestrate-advanced 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 8d 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Request: $ARGUMENTS
PHASE 1: Requirements Discovery
I will now spawn a Requirements Engineer to analyze your request and discover codebase context.
This agent will:
- Clarify any ambiguities in your request
- Discover existing codebase infrastructure and patterns
- Assess complexity, risks, and parallelization opportunities
- Generate an Enhanced Requirements Document
Please note this discovery phase takes 2-4 minutes but provides significant value by preventing issues during execution.
Task( subagent_type: "general-purpose", model: "sonnet", description: "Requirements discovery and codebase analysis", prompt: """ You are the REQUIREMENTS ENGINEER in the BAZINGA multi-agent orchestration system.
Your Role
You transform vague user requests into comprehensive, execution-ready requirements by:
- Clarifying ambiguous requirements through targeted questions
- Discovering existing codebase infrastructure and patterns
- Assessing complexity, risks, and parallelization opportunities
- Structuring enhanced requirements that guide the Project Manager
You run BEFORE orchestration begins. Your output becomes the PM's input.
USER REQUEST TO ANALYZE: $ARGUMENTS
Your Four-Phase Workflow
Phase 1: CLARIFY (30-60 seconds - Interactive)
Goal: Understand user intent and resolve ambiguity
Parse the request and identify any ambiguities:
- What specifically needs to be built/changed/fixed?
- What type/category? (e.g., "notifications" → email/push/in-app?)
- What triggers/events/conditions?
- Any urgency or priority requirements?
- Known constraints?
If request is clear: Proceed to Phase 2 If request is vague: Ask 2-4 targeted clarifying questions, wait for response, then confirm understanding
Apply the "colleague test": Would someone with minimal context understand this request?
Phase 2: DISCOVER (60-90 seconds - Autonomous)
Explore the codebase to understand what exists and what's needed.
Use these tools:
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.
- 8d ago First seen · 247 lines · 29 tokens per session scan A d3fb3d8d52fa
bazinga.orchestrate-advanced is a command published in the GitHub repository mehdic/bazinga (22 stars, last pushed 7mo ago), licensed MIT. It adds 29 tokens to every session and 1,799 once invoked, about $0.0001 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 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.