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 commands/alinaqi/maggy/polyphony-initgit clone --depth 1 https://github.com/alinaqi/maggyWrote 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/commands/alinaqi/maggy/polyphony-init)<a href="https://agentmods.dev/commands/alinaqi/maggy/polyphony-init"><img src="https://agentmods.dev/badge/commands/alinaqi/maggy/polyphony-init.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00333 |
| Opus 5 | $0.00000 | $0.00167 |
| Sonnet 5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
polyphony-init 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 5d 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
/polyphony-init — Setup Wizard
Initialize the Polyphony multi-agent orchestration environment.
Steps
1. Check Prerequisites
command -v docker &>/dev/null || command -v orbctl &>/dev/null
If neither Docker nor OrbStack is available, inform the user:
Docker or OrbStack is required for Polyphony container isolation. Install one first.
2. Create Config Directory
mkdir -p ~/.polyphony
3. Copy Config Templates
Copy default configuration files from the templates directory:
TEMPLATES="$(dirname "$(realpath "$0")")/../templates"
cp -n "$TEMPLATES/polyphony-config.yaml" ~/.polyphony/config.yaml
cp -n "$TEMPLATES/polyphony-identities.yaml" ~/.polyphony/identities.yaml
cp -n "$TEMPLATES/polyphony-agents.yaml" ~/.polyphony/agents.yaml
cp -n "$TEMPLATES/polyphony-routing.yaml" ~/.polyphony/routing.yaml
4. Build Worker Image
docker build -t polyphony-worker:latest -f templates/Dockerfile.polyphony .
5. Detect Available Agents
command -v claude &>/dev/null && echo "claude: available"
command -v codex &>/dev/null && echo "codex: available"
command -v kimi &>/dev/null && echo "kimi: available"
6. Confirm
Print summary of what was initialized and which agents are available.
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.
- 5d ago First seen · 54 lines · 0 tokens per session scan A 2a6595b15d5d
polyphony-init is a command published in the GitHub repository alinaqi/maggy (705 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 333 tokens. 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 commands, from other repositories
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
crear-skill
Crear, probar y mejorar skills de forma iterativa. Usa cuando el usuario dice "crear skill", "crear habilidad", "build skill", "create a skill", "skill development", "desarrollar skill", "nueva habilidad". Usa el workflow: draft → test → review → improve → repeat con evaluación cuantitativa y qualitative review.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
cost-tracker
Track session costs, understand token spend, and get optimization tips.
workpm
PM 모드로 오케스트레이터 시작. 팀을 구성하고 5단계 워크플로우로 작업을 완수합니다.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.