team

A workflow for running independent coding tasks in parallel through separate Oh My MiniMax Code workers. A planner organizes the tasks, while verification remains a separate stage.

In plain words
What is it for?
Use it for multiple independent builder tasks, optionally with separate Git worktrees, and then verify the completed work against its acceptance criteria.
Why use it?
It can reduce waiting when parts of a coding job do not depend on one another, while keeping final checking separate from implementation.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/haoruilee/oh-my-mcode/team
Any agent
npx skills add haoruilee/oh-my-mcode --skill team
Clone the repo
git clone --depth 1 https://github.com/haoruilee/oh-my-mcode

Made for: Claude Code, Codex.

Per session 118 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 612 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00118 $0.00612
Opus 5 $0.00059 $0.00306
Sonnet 5 $0.00024 $0.00122
Haiku 4.5 $0.00012 $0.00061

Measured 2d ago against content hash ceab6453b375, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

skills/team/SKILL.md · 57 lines

What it actually says

Team

Explicit flat team. Sequential max stays the default. Project-manager duties stay in TypeScript. Do not spawn grandchild agents.

This skill does not register host /team. Desktop /team remains the host's Agent Team.

中文名:扁平团队。

Inputs

  • Task / goal.
  • Prefer oh-my-mcode team "<task>" or oh-my-mcode max --team "<task>".
  • MCP first: if omm_* tools exist, use them instead of hand-writing run files. Parallel worktrees may use their own host session (different cwd); the parent run session stays on the workspace.
  • Optional --worktree (git worktree per parallel builder under .minimax/worktrees/<run>/<task>).
  • Concurrency default 2.

Procedure

  1. Same INTAKE → DISCOVER → PLAN as max, but the planner DAG may include independent builders.
  2. The CLI orchestrator schedules ready builders (no unsatisfied deps) in parallel mcode exec workers. You do not spawn children.
  3. Optional worktree: merge back only after that task's verify slice passes. Clean up on cancel.
  4. VERIFY remains a separate phase. Builders never mark Accepted.
  5. Bound concurrency. No 1100-line Sisyphus loop.

Output contract

  • Same run store as max. team_spawned events when a parallel wave starts.
  • Verifier writes Accepted / Rejected.

Failure handling

  • Shared-file conflicts without --worktree: stop and ask for worktrees or a sequential max.
  • Host /team requested: explain coexistence; use this skill only for a durable oh-my-mcode run.

Examples

User: oh-my-mcode team: implement logging and docs if they do not share files

Use the team CLI. Independent builders may run in parallel.

User: /team in the MiniMax desktop

Host feature. Do not claim we registered it.

Changes

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.

  1. 2d ago First seen · 57 lines · 118 tokens per session scan A ceab6453b375

Subscribe to this mod's changes

team is a skill published in the GitHub repository haoruilee/oh-my-mcode (51 stars, last pushed 4d ago), licensed MIT. It adds 118 tokens to every session and 612 once invoked, about $0.0006 per session on Opus 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-08-30.