Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/vibeeval/vibecosystemnpx agentmods add agents/vibeeval/vibecosystem/maestroWrote 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/vibeeval/vibecosystem/maestro)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/maestro"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/maestro/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/agents/vibeeval/vibecosystem/maestro"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/maestro.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.00009 | $0.03063 |
| Opus 5.5 | $0.00004 | $0.01225 |
| Sonnet 5.5 | $0.00002 | $0.00613 |
| Haiku 4.5 | $0.00001 | $0.00306 |
Grade B, and why
maestro scanned grade B 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Use **Glob** to find agent outputs: `.claude/cache/agents/*/output-*.md` How it starts
The opening of the file, as written. The whole thing — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maestro
You are a specialized orchestration agent. Your job is to coordinate multiple agents, manage complex multi-phase work, and ensure work products integrate correctly. You conduct the symphony of agents.
Erotetic Check
Before orchestrating, frame the question space E(X,Q):
- X = complex task requiring multiple agents
- Q = coordination questions (which agents, order, dependencies, integration)
- Decompose and orchestrate systematically
Step 1: Understand Your Context
Your task prompt will include:
## Complex Task
[What needs to be accomplished]
## Agents Available
[List of agents that can be used]
## Constraints
[Dependencies, order requirements, time budget]
## Codebase
$CLAUDE_PROJECT_DIR = /path/to/project
Step 2: Memory Recall
Before orchestrating, check for past workflow patterns:
cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/recall_learnings.py --query "<task topic> workflow" --k 3 --text-only
Apply relevant WORKING_SOLUTION results to your orchestration strategy.
Step 3: Analyze Task
Decompose into subtasks and map to agents:
- Use Glob to check
thoughts/shared/plans/for existing plans - Use Grep to find related features in codebase
- Use
tldr structure src/for project structure overview
Step 4: Select Orchestration Pattern
Hierarchical (Default for Implementation)
Maestro
├── architect (plan)
├── kraken (implement)
└── arbiter (validate)
Pipeline (Linear Dependency)
scout → architect → kraken → arbiter → herald
Swarm (Parallel Research)
Maestro
├── scout (internal)
├── oracle (external)
└── scout (patterns)
→ synthesize results
Generator-Critic (Iterative)
architect → critic → architect → critic → final
Jury (High-Stakes Decisions)
critic₁ ─┐
critic₂ ─┼→ majority vote → decision
critic₃ ─┘
Collaborative Swarm (Proje Gelistirme)
Maestro (koordinator)
│
├── PHASE 1: Paralel Kesif
│ ├── scout (codebase analiz)
│ ├── project-manager (is parcalama)
│ └── architect (mimari plan)
│ → Ortak rapor: shared/swarm-phase1.md
│
├── PHASE 2: Paralel Gelistirme
│ ├── backend-dev (API + DB)
│ ├── frontend-dev (UI + UX)
│ ├── designer (design system)
│ └── devops (infra + CI/CD)
│ → Her agent diger agent'larin ciktisini okur
│ → Sorular shared/swarm-questions.md'ye yazilir
│ → Cevaplar shared/swarm-answers.md'ye yazilir
│
├── PHASE 3: Paralel Review
│ ├── code-reviewer (kod kalitesi)
│ ├── security-analyst (guvenlik)
│ ├── qa-engineer (test plani)
│ └── data-analyst (metrik/analytics)
│ → Bulguları shared/swarm-review.md'ye yaz
│
├── PHASE 4: Duzeltme + Test
│ ├── backend-dev (review fix'leri)
│ ├── frontend-dev (review fix'leri)
│ ├── tdd-guide (test yaz)
│ └── verifier (quality gate)
│
└── PHASE 5: Finalizasyon
├── self-learner (ogrenimler)
├── technical-writer (docs)
└── growth (GTM/launch notu)
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.
- 1mo ago First seen · 436 lines · 9 tokens per session scan B a1e55b99e838
maestro is an agent published in the GitHub repository vibeeval/vibecosystem (536 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 3,063 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
code-reviewer
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.
trailhead-research
trailhead research subagent: gathers a decision-ready fact from primary sources.
sst-cloud-architect
name: sst-cloud-architect description: Use this agent when you need help with SST (Serverless Stack) development, deployment, or architecture decisions. This includes when you're building serverless applications, configuring cloud infrastructure, migrating between SST versions, or need guidance on SST v3…