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/spawn-teamgit 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/spawn-team)<a href="https://agentmods.dev/commands/alinaqi/maggy/spawn-team"><img src="https://agentmods.dev/badge/commands/alinaqi/maggy/spawn-team.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.01990 |
| Opus 5 | $0.00000 | $0.00995 |
| Sonnet 5 | $0.00000 | $0.00398 |
| Haiku 4.5 | $0.00000 | $0.00199 |
Grade B, and why
spawn-team scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
BOOTSTRAP_DIR=$(cat ~/.claude/.bootstrap-dir 2>/dev/null) How it starts
The opening of the file, as written. The whole thing — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/spawn-team - Spawn Agent Team
Spawn the default agent team for this project. Creates a coordinated team of agents that implement features in parallel following the strict TDD pipeline.
Pipeline: Specs > Tests > Ensure tests fail > Implement > Test again > Code Review > Security > Create branch > Create PR
Phase 1: Prerequisites Check
1.1 Detect Container Mode
Check if Polyphony container isolation is available. Container mode is the default when both Docker and polyphony CLI are present.
BOOTSTRAP_DIR=$(cat ~/.claude/.bootstrap-dir 2>/dev/null)
DETECTED_AGENTS=$("$BOOTSTRAP_DIR/scripts/detect-agents.sh" 2>/dev/null || echo "claude")
CONTAINER_MODE="false"
if echo "$DETECTED_AGENTS" | grep -qE "docker|orbstack"; then
if command -v polyphony &>/dev/null; then
CONTAINER_MODE="true"
echo "✓ Container mode: ON (Docker + polyphony detected)"
echo " Each feature agent will run in its own isolated container"
else
echo "⚠ Docker found but polyphony CLI missing"
echo " Run: cd \$(cat ~/.claude/.bootstrap-dir) && ./install.sh"
echo " Falling back to native agents (shared workspace)"
fi
else
echo "ℹ Docker not found — using native agents (shared workspace)"
echo " Install Docker for container isolation: brew install --cask docker"
fi
1.2 Check Agent Definitions
Verify .claude/agents/ exists and has the required agent definitions:
ls .claude/agents/
Required files (with proper frontmatter: name, description, model, tools, disallowedTools, maxTurns):
team-lead.mdquality.mdsecurity.mdcode-review.mdmerger.mdfeature.md
If missing, copy from the agent-teams skill:
cp -r ~/.claude/skills/agent-teams/agents/ .claude/agents/
1.3 Check Feature Specs
ls _project_specs/features/
If no feature specs exist, ask the user:
No feature specs found. The agent team needs features to implement.
What are the key features of this project? I'll create a spec file for each one.
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 · 267 lines · 0 tokens per session scan B e1f798a89adb
spawn-team 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 1,990 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.