maestro

maestro is a plugin for Gemini CLI from josstei/maestro-orchestrate. Its token cost is not measured, scanned A, original, Apache-2.0.

A multi-agent development platform that coordinates specialised coding agents through four phases and keeps session state. It also provides separate workflows for code review, debugging, security, performance, SEO, accessibility, and compliance.

In plain words
What is it for?
Use it to plan and coordinate agent-based implementation, review code, investigate security or performance issues, and manage persistent project sessions.
Why use it?
It organizes different kinds of development work and preserves progress across sessions instead of treating every task as a one-off interaction.

Plugin for Gemini CLI

Written for Gemini CLI: a Gemini CLI extension manifest. Also seen: mentions subagents; mentions Gemini CLI.

Good fit Use it to plan and coordinate agent-based implementation, review code, investigate security or performance issues, and manage persistent project sessions.

Compare 6 plugins from other repositories ↓
Install with agentmods
npx agentmods add plugins/josstei/maestro-orchestrate/gemini-extension
Install

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.

Clone the repo
git clone --depth 1 https://github.com/josstei/maestro-orchestrate

Made for: Gemini CLI.

Wrote 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.

agentmods badge for maestro

README.md
[![agentmods](https://agentmods.dev/badge/plugins/josstei/maestro-orchestrate/gemini-extension/github.svg)](https://agentmods.dev/plugins/josstei/maestro-orchestrate/gemini-extension)
Your own site
<a href="https://agentmods.dev/plugins/josstei/maestro-orchestrate/gemini-extension"><img src="https://agentmods.dev/badge/plugins/josstei/maestro-orchestrate/gemini-extension/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.

agentmods 80×15 button for maestro

Your own site · 80×15
<a href="https://agentmods.dev/plugins/josstei/maestro-orchestrate/gemini-extension"><img src="https://agentmods.dev/badge/plugins/josstei/maestro-orchestrate/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

maestro 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 9d ago.

The scan reads gemini-extension.json. This mod also ships 11 executable files (scripts/check-layer-boundaries.js, scripts/generate.js, scripts/install-codex-plugin.js, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

gemini-extension.json · 57 lines

What it actually says

{
  "name": "maestro",
  "version": "1.6.4",
  "description": "Multi-agent development orchestration platform — 39 specialists, 4-phase orchestration, native parallel subagents, persistent sessions, and standalone review/debug/security/perf/seo/a11y/compliance commands",
  "contextFileName": "GEMINI.md",
  "settings": [
    {
      "name": "Disabled Agents",
      "description": "Comma-separated list of agent names to exclude from implementation planning.",
      "envVar": "MAESTRO_DISABLED_AGENTS"
    },
    {
      "name": "Max Retries",
      "description": "Maximum retry attempts per phase before escalating to user.",
      "envVar": "MAESTRO_MAX_RETRIES"
    },
    {
      "name": "Auto Archive",
      "description": "Automatically archive session state on successful completion (true/false).",
      "envVar": "MAESTRO_AUTO_ARCHIVE"
    },
    {
      "name": "Validation",
      "description": "Post-phase validation strictness level (strict/normal/lenient).",
      "envVar": "MAESTRO_VALIDATION_STRICTNESS"
    },
    {
      "name": "State Directory",
      "description": "Base directory for session state and plans (default: docs/maestro).",
      "envVar": "MAESTRO_STATE_DIR"
    },
    {
      "name": "Max Concurrent",
      "description": "Maximum subagents emitted in one native parallel batch turn (0 = dispatch the entire ready batch).",
      "envVar": "MAESTRO_MAX_CONCURRENT"
    },
    {
      "name": "Execution Mode",
      "description": "Phase 3 execution mode: 'parallel' (native concurrent subagents), 'sequential' (one at a time), or 'ask' (prompt each time). Default: ask.",
      "envVar": "MAESTRO_EXECUTION_MODE"
    }
  ],
  "mcpServers": {
    "maestro": {
      "command": "node",
      "args": [
        "${extensionPath}/mcp/maestro-server.js"
      ],
      "cwd": "${extensionPath}",
      "env": {
        "MAESTRO_RUNTIME": "gemini",
        "MAESTRO_WORKSPACE_PATH": "${workspacePath}"
      }
    }
  }
}
Changes

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.

  1. 9d ago First seen · 57 lines scan A 82ffb1df955d

Subscribe to this mod's changes

maestro is a plugin published in the GitHub repository josstei/maestro-orchestrate (479 stars, last pushed 5d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-10-07.