Multi-Agent Orchestrator

This skill appears to do what it says (patterns and templates for multi-agent orchestration) and is instruction-only, which lowers supply-chain risk. Before installing or using it, check the following: 1) Tool permissions: confirm what host tools the agent will actually have (Read/Write/Bash/WebFetch/WebSearch). If the agent can run Bash or arbitrary web fetches, restrict those tools or run the orchestrations in a sandbox/test repo. 2) Secrets and sensitive files: do not run this against a repo that contains credentials, private keys, or PII unless you trust the environment and have strict agent tooling limits. 3) Review and approvals: require a human approval step for any pipeline that writes to production branches or runs destructive commands. 4) Budget & concurrency: the templates assume spawning many agents and include budget enforcement — set conservative concurrency and budget limits initially to avoid runaway costs. 5) Provenance: the package metadata has no homepage and an unknown source; if provenance matters, try to verify the author's claims and the cited upstream projects before relying on it in production. If you want a lower-risk test: run the orchestrator templates against a small test repository with all tool access disabled except Read, and with human-in-the-loop gating for any write or shell steps.