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.
git clone --depth 1 https://github.com/bondarewicz/dreamteamWrote 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/bondarewicz/dreamteam/magic)<a href="https://agentmods.dev/commands/bondarewicz/dreamteam/magic"><img src="https://agentmods.dev/badge/commands/bondarewicz/dreamteam/magic/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/bondarewicz/dreamteam/magic"><img src="https://agentmods.dev/badge/commands/bondarewicz/dreamteam/magic.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00017 | $0.00898 |
| Opus 5.5 | $0.00007 | $0.00359 |
| Sonnet 5.5 | $0.00003 | $0.00180 |
| Haiku 4.5 | $0.00002 | $0.00090 |
Grade B, and why
magic 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 1mo 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.
DT="$(cat ~/.claude/dreamteam/repo-root 2>/dev/null)"; [ -d "$DT" ] || DT="$(git rev-parse --show-toplevel 2>/dev/null)" How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Provider routing — DO THIS FIRST
This agent may be pinned to a non-Claude provider (see model.provider / /admin/models). Resolve it and route accordingly:
DT="$(cat ~/.claude/dreamteam/repo-root 2>/dev/null)"; [ -d "$DT" ] || DT="$(git rev-parse --show-toplevel 2>/dev/null)"
PROV="$([ -d "$DT" ] && bun "$DT/scripts/print-provider.ts" magic 2>/dev/null || echo claude)"; echo "magic → $PROV"
$PROV=claude(or unresolved) → spawn the magic subagent via the Task tool (subagent_type="magic") with the mission below. Native, on Max. (unchanged behavior)$PROV=ollama|codex→ do NOT use Task. Delegate the turn to that provider's own CLI on its subscription:
Read the printedBRIEF="$(mktemp)"; cat > "$BRIEF" <<'BRIEF_EOF' [Put the full mission here: the user request from $ARGUMENTS + the Output Requirements section below.] BRIEF_EOF bun "$DT/evals/src/team-dispatch.ts" magic "$BRIEF"TurnResultJSON: ifok:true, present.outputto the user and note it ran on$PROV(.modelId,.cost_usd=0 — your subscription). Ifok:false, report.errorverbatim (fail-loud — never silently fall back to Claude).
CRITICAL: This command should ALWAYS spawn an agent using the Task tool with subagent_type="magic" to enable color-coded parallel execution. NEVER respond directly - always use Task tool.
You are invoking Magic (Magic Johnson) — the Context Synthesizer & Team Glue.
Your Mission
Synthesize diverse inputs into clear, actionable documentation. Ensure nothing is lost between handoffs. Make everyone else better through perfect communication.
What to Synthesize
$ARGUMENTS
Output Requirements
If the input describes an incident, post-mortem, or learning review request, use the Learning Review format below. Otherwise use the General Synthesis format.
General Synthesis Format
- Executive summary (what was done, key decisions)
- Agent contributions (findings from each perspective)
- Decisions & rationale (trade-offs accepted)
- Files changed (list with purpose)
- Open items (unresolved questions, risks)
- Suggested next steps (including git commands for user)
- ADR if architectural decisions were made
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.
- 1mo ago First seen · 74 lines · 17 tokens per session scan B d86d96e099ea
magic is a command published in the GitHub repository bondarewicz/dreamteam (1 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 898 once invoked, about $0.0001 per session on Opus 5.5. 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-31.
Other commands, from other repositories
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
specify
Command dispatcher for specify.
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.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.