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/MadAppGang/magusWrote 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/madappgang/magus/team)<a href="https://agentmods.dev/commands/madappgang/magus/team"><img src="https://agentmods.dev/badge/commands/madappgang/magus/team/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/madappgang/magus/team"><img src="https://agentmods.dev/badge/commands/madappgang/magus/team.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.00058 | $0.04021 |
| Opus 5.5 | $0.00023 | $0.01608 |
| Sonnet 5.5 | $0.00012 | $0.00804 |
| Haiku 4.5 | $0.00006 | $0.00402 |
Grade A, and why
team 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Child mode. Check for child mode as claudish:claudish-usage →
"Inside a claudish session (child mode)" describes. In child mode, claudish allows no panel
below this session. Say so in one line, then do the task yourself and report one verdict,
labelled as yours and not a panel vote. If claudish has no tools at all, that is not child
mode: report it as a failure.
Step 1: Setup
Step 1a — Load alias table: Follow the claudish:claudish-usage skill → "Model Alias Resolution" procedure to build ALIAS_TABLE from the live catalog (list_models) + .claude/multimodel-team.json customAliases.
Step 1b — Parse args:
Parse: defaultModels, contextPreferences, agentPreferences, defaultThreshold from prefs.
Parse command args: task, --models, --threshold, --no-memory. If no task: ask the user.
Step 1c — Resolve models (stop at first match, resolve each name via ALIAS_TABLE):
--modelsflag provided → resolve each via ALIAS_TABLEcontextPreferenceskeyword matching task → resolve each via ALIAS_TABLEdefaultModelsfrom prefs → resolve each via ALIAS_TABLE, announce "Using saved models: {list}"- None matched → compose a team from
list_models: takeinternalplus 2–4 current models from different providers, picked for the task type (see table below) - Still nothing → AskUserQuestion listing the models
list_modelscurrently returns
Resolve threshold: unset/"majority" → 50%, "supermajority" → 67%, "unanimous" → 100%
Resolve agent (always — it applies to the whole panel): match task keywords to the
context detection table, check agentPreferences[context] first, else table default, else
dev:researcher. Announce: "Agent: {RESOLVED_AGENT}"
It is passed to team as the agent argument and applies to EVERY model in the run,
native and external alike; there is no per-model form. For a blind panel that is the
correct shape — every voter reviews by the same method, so a vote difference reflects the
model rather than the prompt.
Session directory (the team tool's session path): Bash: SESSION_DIR="$(pwd)/ai-docs/sessions/team-$(date +%Y%m%d-%H%M%S)" && mkdir -p "$SESSION_DIR" && echo "$SESSION_DIR"
Build vote prompt using the template below with {TASK} substituted, then write it
to ${SESSION_DIR}/input.md. Step 2 passes that path, not the text — a vote prompt is
100+ lines, and an inline input echoes every line of it verbatim in the user's terminal,
burying the model list, the agent and the shape check.
Unless --no-memory, save resolved models to defaultModels in the preferences file.
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.
- today Changed · +6 lines 1dfce598dd59
- 10d ago Changed · +39 lines 8665eef0c01d
- 22d ago Changed 0cc2396575c5
- 1mo ago Changed eb82fe5bb123
- 1mo ago First seen · 280 lines · 58 tokens per session scan A 2fd88e30cd6f
team is a command published in the GitHub repository MadAppGang/magus (13 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 4,021 once invoked, about $0.0002 per session on Opus 5.5. 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-09-04.
Other commands, from other repositories
refactor
Systematic code refactoring with smart scope detection.
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.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.