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-spawngit 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-spawn)<a href="https://agentmods.dev/commands/alinaqi/maggy/polyphony-spawn"><img src="https://agentmods.dev/badge/commands/alinaqi/maggy/polyphony-spawn.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.00236 |
| Opus 5 | $0.00000 | $0.00118 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
polyphony-spawn 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 4d 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-spawn — Spawn Task
Create a new task in the Polyphony orchestrator and route it to an agent.
Usage
/polyphony-spawn <title> [--type <task_type>] [--risk <risk>] [--source <source>]
Steps
1. Parse Arguments
title: Required task description--type: Task type (feature, bugfix, docs, refactor, etc.). Default: feature--risk: Risk level (low, medium, high). Default: low--source: Work source (local, github). Default: local
2. Create Task
PYTHONPATH=scripts python3 -m polyphony spawn "$TITLE" --type "$TYPE"
3. Route Task
The orchestrator will automatically:
- Score task complexity (5-dimension scoring)
- Match against routing rules
- Select agent and fallback chain
- Provision container with workspace
- Start agent execution
4. Report
Print task ID and routing decision.
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.
- 4d ago First seen · 40 lines · 0 tokens per session scan A 70f535167372
polyphony-spawn is a command published in the GitHub repository alinaqi/maggy (705 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 236 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
frappe-backend
Treat the task as Frappe backend work.
py-harden
Scan Python backend code for anti-patterns and fix them. Runs the full anti-pattern catalog (AP-01 through AP-22) against the codebase.
py-structure
Analyze and recommend project structure improvements. Checks file sizes, layer organization, module splitting, and hexagonal architecture compliance.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.