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/worktree)<a href="https://agentmods.dev/commands/restarter/lets-workflow/worktree"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/worktree/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/worktree"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/worktree.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.00016 | $0.12598 |
| Opus 5.5 | $0.00006 | $0.05039 |
| Sonnet 5.5 | $0.00003 | $0.02520 |
| Haiku 4.5 | $0.00002 | $0.01260 |
Grade A, and why
worktree 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 — 657 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worktree Management
Thin dispatcher for interactive parallel worktrees. All filesystem/git work lives in the Go subcommand lets worktree (cli/internal/worktreecmd/); this skill captures user intent via AskUserQuestion, shells out with --json, and renders the result.
Interactive worktrees only. Agent worktrees (isolation: worktree) use native Claude Code behavior — not this command.
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:worktree create auth-feature), parse it:
create --team [<callsign>] --area <a>-> go to Create a team (a standing team's worktree and its lead). Strip--team, the optional<callsign>,--area <a>, the launcher overrides (--orca/--no-orca/--cmux/--no-cmux/--tmux/--no-tmux) and the launch-mode flags (--launch-mode <m>/--auto/--all-in- the lead's Launch mode below). Refused with one line, then stop: together with--flow(a team's lead starts interactively, on no flow), and from inside a worktree.create <name>-> go to Create. First strip any--orca/--no-orca/--cmux/--no-cmux/--tmux/--no-tmux/--launch-mode <m>/--auto/--all-in/--flow <value>/--branch <ref>/--title-file <path>token out of the argument and carry them as overrides (--orca/--no-orca= the Orca launcher, Step C0;--cmux/--no-cmux/--tmux/--no-tmux= launcher;--launch-mode/--auto/--all-in= the Launch mode below;--flow plan|plan-workflow= which command the launch lands in — all for Steps C0 / C3.5;--branch <ref>decouples the attached/created branch from the dir name — Step C2;--title-file <path>= a file holding the task title, passed bytake-taskso the branch name is derived in Go — Step C1). Bind the remainder as<name>(socreate auth --flow plan-workflow --auto=> nameauth, not the flags;create pwa-46696 --branch feature/pwa-46696=> namepwa-46696, branchfeature/pwa-46696). A<name>that is a bare task id (it passes the detect-task id gate andtake-tasksent it) means From task in Step C1 with that id.list-> go to Listremove <name>-> go to Removeinfo-> go to Info
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 55c9e736ee69
- 3d ago Changed · +12 lines 274168cc3270
- 10d ago Changed e5c691a54d1b
- 20d ago Changed · +146 lines 9a81e732571a
- 28d ago Changed · +1 lines 726e84dd5d8a
- 1mo ago Changed · +66 lines de371e936d49
- 1mo ago First seen · 432 lines · 16 tokens per session scan A 0e1dc3ad2cf8
worktree is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 12,598 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
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.
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
pr
Prepare and open a pull request the senior way: gate, template, scrubbed, everything visible.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.