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)<a href="https://agentmods.dev/commands/restarter/lets-workflow/plan"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/plan/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"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/plan.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.00017 | $0.08824 |
| Opus 5.5 | $0.00007 | $0.03530 |
| Sonnet 5.5 | $0.00003 | $0.01765 |
| Haiku 4.5 | $0.00002 | $0.00882 |
Grade A, and why
plan 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 — 871 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan
Turn a task or idea into a detailed implementation plan. Clarifies scope, explores codebase, discusses approaches with user, designs architecture for selected approaches, evaluates with experts, then writes a bite-sized plan.
HARD-GATE: This command produces a plan, NOT code. No files are modified except .lets/plans/ and the agent report files under .lets/reports/ that the agent-report skill names. The command ENDS when the plan is saved - implementation starts ONLY when the user runs /lets:execute. Nothing the user says after the plan ("ok", "approved", a question) starts it.
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.
--fast mode
/lets:plan --fast (combinable with a task-id or feature description, e.g. /lets:plan lets-abc --fast) skips the three subagent-dispatch phases - Step 4 (explorer agents), Step 6 (architect agents), Step 7 (expert agents) - and replaces them with orchestrator-only equivalents (read files yourself, draft approaches inline, self-evaluate risks). Use it when the user explicitly wants a collaborative talk-through without subagent budget: "let's just plan it together, I'll review". Everything else - clarifying questions, interactive discussion, plan format, tracker recording, the saved file - is identical to the full flow. The plan's shape doesn't change; only how it's built.
When --fast is not set, run the full flow exactly as written.
--idea mode
/lets:plan --idea (combinable with a task-id; --fast is a no-op here, no agents run anyway) writes a concept document, not a plan: the wish, captured before anyone decides how to build it. /lets:execute never picks it up and refuses it by path; a later /lets:plan on the same task reads it as input.
| Step | In --idea mode |
|---|---|
| 3 | Questions about the wish: who wants it, why, how it should feel, what triggers it, what is out of scope, who takes it over (the handoff target) |
| 4, 6, 7 | SKIPPED - no codebase exploration, no architecture, no experts; no code snippets or file paths anywhere in the document |
| 5 | Discuss behaviour variants the user would notice, not implementations |
| 9 | The idea template below - NO STOP banner (there is nothing to execute) |
| 10 | Save via Skill(skill: "lets:artifact-path", args: "kind=idea ext=md task={TASK_ID}") and record it (below) |
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 e130ef109215
- 15d ago Changed · +4 lines 070a6c214ba9
- 19d ago Changed · +4 lines f46fda3aadff
- 20d ago Changed · +25 lines 2e64e094784b
- 23d ago Changed d4df956cce42
- 28d ago Changed · +7 lines 64fd22654626
- 1mo ago Changed · +46 lines 01cc19a63f9a
- 1mo ago First seen · 785 lines · 17 tokens per session scan A 0767c63fe084
plan is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 8,824 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.