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/josstei/maestro-orchestrateWrote 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/plugins/josstei/maestro-orchestrate/claude)<a href="https://agentmods.dev/plugins/josstei/maestro-orchestrate/claude"><img src="https://agentmods.dev/badge/plugins/josstei/maestro-orchestrate/claude/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/plugins/josstei/maestro-orchestrate/claude"><img src="https://agentmods.dev/badge/plugins/josstei/maestro-orchestrate/claude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 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.
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.
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",
"author": {
"name": "josstei",
"email": "[email protected]",
"url": "https://github.com/josstei"
},
"license": "Apache-2.0",
"hooks": "./hooks/claude-hooks.json",
"mcpServers": "./.mcp.json",
"homepage": "https://github.com/josstei/maestro-orchestrate",
"repository": "https://github.com/josstei/maestro-orchestrate",
"keywords": [
"orchestration",
"multi-agent",
"planning",
"execution"
]
}
What it installs
The manifest is a name and a version. 19 skills, 33 agents, 1 MCP server travel with it, and installing the plugin installs all of them — 8,941 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill execute A 14 tokens
- Skill orchestrate A 31 tokens
- Skill resume-session A 18 tokens
- Skill a11y-audit A 28 tokens
- Skill review-code A 18 tokens
- Skill security-audit A 25 tokens
- Skill archive A 13 tokens
- Skill compliance-check A 25 tokens
- Skill debug-workflow A 13 tokens
- Skill perf-check A 18 tokens
- Skill seo-audit A 25 tokens
- Skill status A 13 tokens
- Skill code-review A 15 tokens
- Skill delegation A 17 tokens
- Skill execution A 15 tokens
- Skill implementation-planning A 12 tokens
- Skill validation A 14 tokens
- Skill design-dialogue A 13 tokens
- Skill session-management A 15 tokens
- Agent accessibility-specialist A 272 tokens
- Agent cobol-engineer A 294 tokens
- Agent compliance-reviewer A 259 tokens
- Agent integration-engineer A 312 tokens
- Agent ml-engineer A 268 tokens
- Agent mlops-engineer A 271 tokens
- Agent mobile-engineer A 263 tokens
- Agent observability-engineer A 274 tokens
- Agent platform-engineer A 264 tokens
- Agent analytics-engineer A 234 tokens
- Agent api-designer A 215 tokens
- Agent cloud-architect A 272 tokens
- Agent code-reviewer A 207 tokens
- Agent content-strategist A 253 tokens
- Agent data-engineer A 218 tokens
- Agent database-administrator A 277 tokens
- Agent db2-dba A 303 tokens
- Agent design-system-engineer A 254 tokens
- Agent devops-engineer A 227 tokens
- Agent hlasm-assembler-specialist A 306 tokens
- Agent i18n-specialist A 263 tokens
- Agent ibm-i-specialist A 303 tokens
- Agent performance-engineer A 221 tokens
- Agent product-manager A 228 tokens
- Agent release-manager A 278 tokens
- Agent security-engineer A 222 tokens
- Agent seo-specialist A 250 tokens
- Agent site-reliability-engineer A 280 tokens
- Agent solutions-architect A 262 tokens
- Agent technical-writer A 225 tokens
- Agent ux-designer A 232 tokens
- Agent zos-sysprog A 305 tokens
- Agent prompt-engineer B 287 tokens
- MCP server maestro A not measured
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 · 22 lines scan A fbe4e0ac9ab7
maestro is a plugin published in the GitHub repository josstei/maestro-orchestrate (484 stars, last pushed 6d 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-08-30.
Other plugins, from other repositories
gemini
Gemini via Antigravity CLI for Claude Code — ask, review, adversarial-review, implement.
gemini
Use Gemini CLI from Claude Code to review code or delegate tasks.
gemini-as-tool
Use Google Gemini (3.x Pro/Flash) as a headless tool, builder, or judge from Claude Code — via Google AI Pro OAuth, no API key.
cloud-sql-postgresql
Create, connect, and interact with a Cloud SQL for PostgreSQL database and data.
ask-llm
AI-to-AI collaboration — review code and debate plans across Codex, Grok, Antigravity, Ollama, and Gemini.
knowledge-catalog
Connect to Knowledge Catalog to discover, manage, monitor, and govern data and AI artifacts across your data platform.