team

team is a command for Claude Code from restarter/lets-workflow. It costs 19 tokens per session (12,778 once invoked), scanned A, original, MIT.

A command for splitting independent coding tasks among several AI teammates, each working in a separate copy of the project.

In plain words
What is it for?
Use it for parallel implementation work, such as having separate teammates handle unrelated features or fixes.
Why use it?
It lets multiple tasks be implemented at the same time while keeping their changes isolated. You can also check progress or stop the team.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions subagents; names the AskUserQuestion tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the lets plugin — 20 skills, 26 commands, 16 agents shipped together

Good fit Use it for parallel implementation work, such as having separate teammates handle unrelated features or fixes.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add restarter/lets-workflow
Claude Code
/plugin install lets

Made for: Claude Code.

Or install lets, the plugin that ships this one along with the rest of its 20 skills, 26 commands, 16 agents.

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/commands/restarter/lets-workflow/team/github.svg)](https://agentmods.dev/commands/restarter/lets-workflow/team)
Your own site
<a href="https://agentmods.dev/commands/restarter/lets-workflow/team"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/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/commands/restarter/lets-workflow/team"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 12,778 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.00019 $0.12778
Opus 5.5 $0.00008 $0.05111
Sonnet 5.5 $0.00004 $0.02556
Haiku 4.5 $0.00002 $0.01278

Measured today against content hash cb9c937eb8e3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

plugins/lets/commands/team.md · 730 lines

How it starts

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

Team

Run several independent tasks at once: each task gets its own worktree and its own visible LETS session (a worker), bound to this session as its orchestrator. The worker's own human presses every gate in the worker's terminal; this session coordinates through the orc skill and never decides for a worker.

This is for parallel implementation of independent tasks. For analysis (review, opinion, plan) - use their dedicated commands.

IMPORTANT: If the spec below invokes any deferred tool (e.g. AskUserQuestion), you MUST load and call it as specified. Never skip the call, never substitute a default answer of your own — the tool invocation is part of the contract. This is critical.

Step 1: Determine Subcommand

If argument provided (e.g., /lets:team run), parse it:

  • run -> go to Run (pass remaining flags like --tasks A,B,C to Step R2; --launch-mode <m> / --auto / --all-in set the workers' launch mode, Step R4.5)
  • spawn <role> [name] / spawn --roster -> go to Spawn
  • dismiss <name> / dismiss --all -> go to Dismiss
  • roster -> go to Roster
  • status -> go to Status
  • stop -> go to Stop
  • create [<callsign>] --area <a> -> go to Create (carry --orca / --cmux / --tmux and --launch-mode <m> / --auto / --all-in with it)
  • disband <callsign> -> go to Disband

If no argument, use AskUserQuestion:

AskUserQuestion(
  questions=[{
    question: "What do you want to do with the team?",
    header: "Team",
    options: [
      { label: "Run", description: "Open one worker session per task, bound to this session" },
      { label: "Roster", description: "Show the standing team's members and who is live" },
      { label: "Status", description: "Show the roster, each worker's state and tracker status" },
      { label: "Stop", description: "Ask every worker to end its session; worktrees stay" }
    ],
    multiSelect: false
  }]
)

Run

Select tasks, register this session as their orchestrator, open one worker session per task, record the run.

Read the full file on GitHub · 730 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. today Changed cb9c937eb8e3
  2. 2d ago Changed · +3 lines 25b39bb1ee7e
  3. 3d ago Changed · +31 lines 902f9d5fc5be
  4. 10d ago Changed 9871a22f0e67
  5. 19d ago Changed · +6 lines 352a8c6a5d29
  6. 20d ago Changed · +32 lines · +7 tokens per session d0084958ef5d
  7. 1mo ago Changed · +48 lines c3afc8fc8e45
  8. 1mo ago First seen · 610 lines · 12 tokens per session scan A 3e72c5d43baa

Subscribe to this mod's changes

team is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 12,778 once invoked, about $0.0001 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-08-30.