agentmods.dev

team

team is a skill for Claude Code, Codex from mrzhangguoguo/oh-my-workbuddy. It costs 43 tokens per session (5,905 once invoked), scanned A, original, MIT.

A coordination workflow for assigning parts of a coding task to multiple agents that share a task board.

In plain words
What is it for?
Running parallel work lanes, combining their results, and tracking each lane's status in a shared task list.
Why use it?
It helps divide large or independent pieces of work while keeping delivery and verification coordinated.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; names the AskUserQuestion tool; mentions Codex.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/lizhi/.workbuddy/teams/<team-name>.json.

not rated 2repo 2mo ago A scan 43 tokens original MIT

Good fit Running parallel work lanes, combining their results, and tracking each lane's status in a shared task list.

Compare 6 skills from other repositories ↓
View source ↗ mrzhangguoguo/oh-my-workbuddy
Install

Getting it into your agent

There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for team

README.md
[![agentmods](https://agentmods.dev/badge/skills/mrzhangguoguo/oh-my-workbuddy/team/github.svg)](https://agentmods.dev/skills/mrzhangguoguo/oh-my-workbuddy/team)
Your own site
<a href="https://agentmods.dev/skills/mrzhangguoguo/oh-my-workbuddy/team"><img src="https://agentmods.dev/badge/skills/mrzhangguoguo/oh-my-workbuddy/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.

agentmods 80×15 button for team

Your own site · 80×15
<a href="https://agentmods.dev/skills/mrzhangguoguo/oh-my-workbuddy/team"><img src="https://agentmods.dev/badge/skills/mrzhangguoguo/oh-my-workbuddy/team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,905 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00043 $0.05905
Opus 5 $0.00022 $0.02952
Sonnet 5 $0.00009 $0.01181
Haiku 4.5 $0.00004 $0.00590

Measured 11d ago against content hash 89d29d3d346c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 11d 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 · 476 lines

How it starts

The opening of the file, as written. The whole thing — 476 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ported from oh-my-codex team. OMX runtime conventions ($macro invocation, omx team CLI, tmux panes, .omx/ state directory) are replaced with WorkBuddy idioms (TeamCreate, Agent tool, SendMessage, Task tools, .workbuddy/ memory).

Team Skill

team is WorkBuddy's coordinated multi-agent execution mode. There is no tmux runtime and no omx team CLI — coordination is built from the TeamCreate tool (team + shared task board), the Agent tool (teammates), the SendMessage tool (mailbox/dispatch), and the Task tools (single source of truth). Treat this skill as an operator workflow, not a generic prompt pattern.

In non-team surfaces (plain single-session chat without a created team), do not present team as directly available; first call TeamCreate, or stay on the nearest single-agent surface until the user explicitly wants the multi-agent runtime.

Team vs Native Subagents

  • Use a single Agent tool call (or a few run in parallel) for bounded, in-session parallelism where one leader thread can fan out a few independent subtasks and wait for them directly, with no shared mutable files.
  • Use team when you need durable shared task state, explicit handoffs, role separation (delivery vs. verification), cross-boundary ownership, or long-running parallel execution that must stay tracked across the session and survive beyond one local reasoning burst.
  • Native Agent fan-out can complement team execution, but it does not replace the team runtime's stateful coordination contract (shared task board, mailbox, lifecycle control).

What This Skill Must Do

When the user triggers team, the leader (you) must:

  1. Call TeamCreate to establish the team + task board (creates /Users/lizhi/.workbuddy/teams/<team-name>.json and /Users/lizhi/.workbuddy/tasks/<team-name>/).
  2. Build the shared task board with TaskCreate — one task per work item, with subject, description, owner, and addBlockedBy/addBlocks for dependencies.
  3. Fan out teammates with the Agent tool, each given: team_name, a unique name, a subagent_type/description, the goal, its claimed task id(s), the relevant file paths, and a precise "report back" contract.
  4. Verify startup and surface concrete state/board evidence.
  5. Keep the team state alive until every teammate is terminal (unless explicit abort).
  6. Handle cleanup and stale-teammate recovery when needed.

Read the full file on GitHub · 476 lines

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. 11d ago First seen · 476 lines · 43 tokens per session scan A 89d29d3d346c

Subscribe to this mod's changes

team is a skill published in the GitHub repository mrzhangguoguo/oh-my-workbuddy (2 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 5,905 once invoked, about $0.0002 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-31.

Building agentsProject managementagent-skillsexecutionoh-my-codexskillsworkbuddy
Related

Other skills, from other repositories

dispatch

Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it"…

jeremylongshore/tons-of-skills-marketplace · 81 tokens

syndic

Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…

romainsimon/paperasse · 194 tokens

flow-next-plan

Plan a feature into a flow-next spec with tasks in .flow/. Use when asked to plan, spec out, or break down work (fn-N ids).

gmickel/flow-next · 36 tokens

template-instantiation

Creates .NET projects from templates with validated parameters, smart defaults, Central Package Management adaptation, and latest NuGet version resolution. USE FOR: creating new dotnet projects, scaffolding solutions with multiple projects, installing or uninstalling template packages, creating projects that respect…

managedcode/dotnet-skills · 168 tokens

project-execution

Executes implementation plans with progress tracking, checkpoint validation, and quality gates. Use after planning is complete and tasks are ready to implement.

athola/claude-night-market · 31 tokens

note-improvement

Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…

tobihagemann/turbo · 107 tokens