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.
/plugin marketplace add restarter/lets-workflow/plugin install letsWrote 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/restarter/lets-workflow/team)<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.
<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>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.00019 | $0.12778 |
| Opus 5.5 | $0.00008 | $0.05111 |
| Sonnet 5.5 | $0.00004 | $0.02556 |
| Haiku 4.5 | $0.00002 | $0.01278 |
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 — 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,Cto Step R2;--launch-mode <m>/--auto/--all-inset the workers' launch mode, Step R4.5)spawn <role> [name]/spawn --roster-> go to Spawndismiss <name>/dismiss --all-> go to Dismissroster-> go to Rosterstatus-> go to Statusstop-> go to Stopcreate [<callsign>] --area <a>-> go to Create (carry--orca/--cmux/--tmuxand--launch-mode <m>/--auto/--all-inwith 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.
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 cb9c937eb8e3
- 2d ago Changed · +3 lines 25b39bb1ee7e
- 3d ago Changed · +31 lines 902f9d5fc5be
- 10d ago Changed 9871a22f0e67
- 19d ago Changed · +6 lines 352a8c6a5d29
- 20d ago Changed · +32 lines · +7 tokens per session d0084958ef5d
- 1mo ago Changed · +48 lines c3afc8fc8e45
- 1mo ago First seen · 610 lines · 12 tokens per session scan A 3e72c5d43baa
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.
Other commands, from other repositories
audit-security
Check baseline CI security hygiene against the Starter Series bar — gitleaks, CodeQL, dep audit, license check, --ignore-scripts, Dependabot grouped, secret-scanning, claude-code-security-review, claude-security-guidance. Read-only, complementary to Anthropic's in-session security guidance plugin.
code-quality-plan-creator
LSP-powered architectural code quality analysis - works with any executor (loop or swarm).
mr-description-creator
Generate and apply MR/PR description directly via gh or glab CLI (project).
agy-review
Send the current change set to Antigravity (agy) for a senior-reviewer code review.
review
Two-stage code review (spec compliance + code quality).
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.