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/plan-workflow)<a href="https://agentmods.dev/commands/restarter/lets-workflow/plan-workflow"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/plan-workflow/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/plan-workflow"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/plan-workflow.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.00038 | $0.04744 |
| Opus 5.5 | $0.00015 | $0.01898 |
| Sonnet 5.5 | $0.00008 | $0.00949 |
| Haiku 4.5 | $0.00004 | $0.00474 |
Grade A, and why
plan-workflow 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonomous Plan (PREVIEW workflow)
PREVIEW / experimental. Shipped standalone so the autonomous-planning Dynamic Workflow can be dogfooded across projects and gather edits before it's folded into native /lets:plan --workflow (tracked in lets-jsw00). The reusable artifact is skills/plan-workflow/plan.workflow.js; this command is a thin dispatcher. The interactive native /lets:plan is untouched. Expect rough edges - report them.
Autonomous whole-command planning: you give a GOAL + a RUBRIC up front; the workflow explores, proposes approaches, architects each, judges them against your rubric, evaluates the winner, and writes a plan - all off-context. You approve the plan at the end. Steer-by-rubric + approve-at-end, not gate-each-step.
IMPORTANT: Deferred tools (e.g.
AskUserQuestion) must be loaded and called as specified.
Step 0: Resolve & claim (spawn entry)
If the argument is an explicit task id - a single token matching the ACTIVE tracker's id shape per the detect-task convention (beads: <prefix>-<alphanum>[.N]; a numeric-id tracker: a pure-numeric id; do NOT hardcode the beads regex on a non-beads project) - rather than a free-text goal - as the autonomous pipeline launches it (/lets:plan-workflow <id> into a fresh worktree) - resolve-and-claim per the detect-task convention: treat the id as authoritative and, if the tracker's show reports <id> not in_progress, Skill(skill: "lets:take-task", args: "<id>") to claim it (the spawn-time entry claim is AUTO-MODE-exempt - see detect-task/SKILL.md). Then derive the GOAL from the task title + description for Step 1. A free-text goal argument skips this step (no claim). --orc is stripped per the detect-task convention before the task-id test.
Pipeline-state marker (spawn-claimed runs only)
When Step 0 spawn-claimed a task (the autonomous pipeline launched this), record the phase in a per-task marker so N parallel worktrees don't collide and the gate-notify can tell autonomous from interactive. Per-task filename (NOT a shared pipeline-state — .lets/ is a symlink across worktrees): .lets/cache/pipeline-state-<task-id>, line <task-id>|<phase>|<iso>, phase ∈ planning | gate-clarify | gate-approve | executing | blocked | done. Helper:
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.
- 2d ago Changed · +1 lines 974aa0782198
- 19d ago Changed c55645a40584
- 23d ago Changed bc59ec68b66c
- 28d ago Changed · +3 lines 9e0123489a3d
- 1mo ago Changed · +47 lines 84f67bd23b82
- 1mo ago First seen · 125 lines · 38 tokens per session scan A a999f4973691
plan-workflow is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 4,744 once invoked, about $0.0002 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
todo
The quality-gated task list: tasks with real descriptions, testable acceptance criteria, and evidence — a task only closes when the controller agrees it is done.
develop
Implement skill development issues with TDD-governed workflow.
release-flow
Portable gated release flow — deterministic gate + vendor-agnostic independent reviewer, runnable from any harness.
triage-inbox
Sort application mail into the freehire tracker and drain the link queues.
retro
Score zforge's workflow performance on a feature.
audit-release
Diagnose release-readiness against the Starter Series quality bar — matched starter, version-vs-last-tag drift, CHANGELOG drift vs merged PRs, and publish-workflow kind. Read-only.