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.
npx agentmods add plugins/josstei/maestro-orchestrate/marketplace/plugin marketplace add josstei/maestro-orchestrategit clone --depth 1 https://github.com/josstei/maestro-orchestrateGrade A, and why
maestro-orchestrator 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 yesterday.
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-orchestrator",
"owner": {
"name": "josstei"
},
"metadata": {
"description": "Maestro multi-agent orchestration platform for Claude Code",
"version": "1.6.4"
},
"plugins": [
{
"name": "maestro",
"source": "./claude",
"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",
"version": "1.6.4",
"author": {
"name": "josstei",
"email": "[email protected]",
"url": "https://github.com/josstei"
},
"homepage": "https://github.com/josstei/maestro-orchestrate",
"repository": "https://github.com/josstei/maestro-orchestrate",
"license": "Apache-2.0",
"keywords": [
"orchestration",
"multi-agent",
"planning",
"execution",
"agents"
],
"category": "productivity"
}
]
}
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.
- yesterday First seen · 35 lines scan A 4e91d4228df5
maestro-orchestrator is a plugin published in the GitHub repository josstei/maestro-orchestrate (459 stars, last pushed 25d 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
cloud-sql-postgresql-marketplace
Plugin marketplace listing 1 plugin: cloud-sql-postgresql.
knowledge-catalog
Connect to Knowledge Catalog to discover, manage, monitor, and govern data and AI artifacts across your data platform.
knowledge-catalog-marketplace
Plugin marketplace listing 1 plugin: knowledge-catalog.
firestore-native
Connect and interact with Firestore databases, collections, and documents.
firestore-native-marketplace
Plugin marketplace listing 1 plugin: firestore-native.
alloydb
Create, connect, and interact with an AlloyDB for PostgreSQL database and data.