teammode

Codex-only team orchestration: run a named team of cooperating Codex workers with durable, script-managed state. MUST USE when the user asks Codex to create, run, coordinate, inspect, archive, or delete a team of agents/threads/sessions, or to work on something as a team in parallel. FIRST inspects the active tool surface (checking tool_search for deferred tools) and tells the user the route: native MultiAgentV2 agents (flat spawn_agent with task_name) when available, Codex App threads as the fallback, or a plain-subagent split when neither set exists. The main session is always the leader; members are defined by a concrete part, ownership area, or perspective - never a vague job role; a bundled cross-platform script writes the .omo/teams state plus an auto-generated member field manual. Use a team when the work is not perfectly isolated but parallelizing helps; use plain subagents when scope is perfectly isolated or the goal is ambiguous. Triggers: team mode, teammode, make a team, run as a team, team of agents, coordinate threads, parallel Codex threads, archive the team.

by code-yeongyu 69k GitHub stars Other Updated Sep 21, 2026
↑ GrowingActive Workflow CodexCursorOpenCode ⚠ No license
teammode skill by code-yeongyu
teammode — Workflow skill by code-yeongyu

Overview

teammode is an open-source workflow skill for Codex, published by code-yeongyu. Its author describes it as: “Codex-only team orchestration: run a named team of cooperating Codex workers with durable, script-managed state. MUST USE when the user asks Codex to create, run, coordinate, inspect, archive, or delete a team of agen…”. The project has 69k stars on GitHub and ships custom license terms, so review them before reuse. Add it to your setup with `git clone https://github.com/code-yeongyu/oh-my-openagent ~/.claude/skills/teammode`.

What teammode does

Run a named team of cooperating Codex workers under one leader, with durable state on disk. This is a Codex-only workflow. It never depends on an external terminal runner - it coordinates through Codex's own collaboration tools plus a bundled state script, on ONE of two transports chosen up front: native MultiAgentV2 agents, or Codex App threads as the fallback.

What’s inside

The SKILL.md for teammode is organised into these sections:

  • When to use a team (and when to use plain subagents instead)
  • Pick the transport FIRST - then tell the user
  • You are the leader - orchestrate, do not implement
  • Compose by part, ownership, or perspective - not by job title
  • Run the script - never hand-write team state
  • Create the team and its members
  • Communication
  • Let members work - do not rush them
  • Worktrees - isolate members who would touch the same files
  • Run a ulw-plan in parallel
  • Archive, delete, and cleanup
  • Stop rules

Installation

Add teammode to your agent with:

git clone https://github.com/code-yeongyu/oh-my-openagent ~/.claude/skills/teammode

Review a skill’s source before installing it — skills can instruct your agent to run commands. This command comes from the skill’s public repository, which is the source of truth for setup steps. New to skills? Read how to install Claude Code skills.

Supported agents

  • Codex — named in the skill.md
  • Cursor — declared in the repository topics
  • OpenCode — declared in the repository topics

License

code-yeongyu has not declared a standard open-source license for this repository (Other). Confirm the terms with the author before reusing it.

Strengths

  • Ships in code-yeongyu/oh-my-openagent, an established project with 69,248 GitHub stars
  • Works with Codex, Cursor, OpenCode
  • Actively maintained — repository updated in the last 30 days
  • Its repository gained 2,357 GitHub stars over the last 52 days

Things to check

  • No license declared — confirm terms with the author before reuse

Author

code-yeongyu 49 skills in the catalog · GitHub profile ↗
View skills

Topics

Need a skill like this, tailored to your team?Build a custom skill →

Frequently asked questions

What does teammode do?
Codex-only team orchestration: run a named team of cooperating Codex workers with durable, script-managed state. MUST USE when the user asks Codex to create, run, coordinate, inspect, archive, or delete a team of agents/threads/sessions, or to work on something as a team in parallel. FIRST inspects the active tool surface (checking tool_search for deferred tools) and tells the user the route: native MultiAgentV2 agents (flat spawn_agent with task_name) when available, Codex App threads as the fallback, or a plain-subagent split when neither set exists. The main session is always the leader; members are defined by a concrete part, ownership area, or perspective - never a vague job role; a bundled cross-platform script writes the .omo/teams state plus an auto-generated member field manual. Use a team when the work is not perfectly isolated but parallelizing helps; use plain subagents when scope is perfectly isolated or the goal is ambiguous. Triggers: team mode, teammode, make a team, run as a team, team of agents, coordinate threads, parallel Codex threads, archive the team.
How do I install teammode?
Run git clone https://github.com/code-yeongyu/oh-my-openagent ~/.claude/skills/teammode in your agent, then reload your skills. Review the source at https://github.com/code-yeongyu/oh-my-openagent before installing.
Is teammode free to use?
teammode is publicly available on GitHub, but code-yeongyu has not declared a standard open-source license (Other). Confirm the terms with the author before reusing it.
Which agents does teammode work with?
teammode lists Codex, Cursor, and OpenCode — named in its SKILL.md, its plugin marketplace or its repository topics. Skills use the portable SKILL.md format, so other agents that read that format may load it too.
Where does teammode come from?
teammode ships inside code-yeongyu/oh-my-openagent, a repository that contains 49 catalogued skills in total. The repository's 69,248 GitHub stars apply to that whole collection, not to this skill on its own.

Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.

↑ GrowingActive CodexCursorOpenCode
69k GitHub stars Other Updated Sep 21, 2026 Free

Easter egg command - about oh-my-opencode. Triggers: omomomo, about, easter egg.

↑ GrowingActive CodexCursorOpenCode
69k GitHub stars Other Updated Sep 21, 2026 Free

Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release synthesis. Runs ONLY when the user explicitly asks for a pre-publish review — a plain publish/release request MUST NOT trigger this; /publish ships directly. Triggers: 'pre-publish review', 'review before publish', 'release review', 'pre-release review', 'ready to publish?', 'can I publish?', 'pre-publish', 'safe to publish', 'publishing review', 'pre-publish check'.

↑ GrowingActive CodexCursorOpenCode
69k GitHub stars Other Updated Sep 21, 2026 Free

Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: <patch|minor|major|explicit-semver>. Triggers: publish, release, deploy, npm publish.

↑ GrowingActive CodexCursorOpenCode
69k GitHub stars Other Updated Sep 21, 2026 Free

Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.

↑ GrowingActive CodexCursorOpenCode
69k GitHub stars Other Updated Sep 21, 2026 Free