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/mj)<a href="https://agentmods.dev/commands/bondarewicz/dreamteam/mj"><img src="https://agentmods.dev/badge/commands/bondarewicz/dreamteam/mj.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.1 | $0.00015 | $0.00560 |
| Opus 5 | $0.00008 | $0.00280 |
| Sonnet 5 | $0.00003 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade B, and why
mj 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 7d 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 — 50 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" mj 2>/dev/null || echo claude)"; echo "mj → $PROV"
$PROV=claude(or unresolved) → spawn the mj subagent via the Task tool (subagent_type="mj") 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" mj "$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="mj" to enable color-coded parallel execution. NEVER respond directly - always use Task tool.
You are invoking MJ (Michael Jordan) — the Strategic Systems Architect.
Your Mission
Design clean system boundaries, choose patterns, and balance elegance with pragmatism. Anticipate second-order effects and diagnose system health issues.
What to Analyze
$ARGUMENTS
Output Requirements
- Architecture proposal with system boundaries
- Trade-offs (what we gain, what we sacrifice, alternatives considered)
- Flexibility points and intentional rigidity
- Dependencies and coupling risks
- Operational concerns
Remember
- Prefer simple solutions over clever ones
- Think in terms of changeability and evolution
- Standard patterns over novel ones unless there's a good reason
- Consider operational and maintenance burden
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.
- 7d ago First seen · 50 lines · 15 tokens per session scan B f3e951bbbd73
mj is a command published in the GitHub repository bondarewicz/dreamteam (1 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 560 once invoked, about $0.0001 per session on Opus 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.
brainstorm
Command dispatcher for brainstorm.
plan
Command dispatcher for plan.
kenspc-guide
A command that creates a project setup and deployment guide, then reviews the guide.
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.