Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/restarter/lets-workflow/plan-workflownpx skills add restarter/lets-workflow --skill plan-workflowgit clone --depth 1 https://github.com/restarter/lets-workflowWhat 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 | $0.00051 | $0.01920 |
| Opus 5 | $0.00026 | $0.00960 |
| Sonnet 5 | $0.00010 | $0.00384 |
| Haiku 4.5 | $0.00005 | $0.00192 |
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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
plan-workflow (PREVIEW Dynamic Workflow asset)
Preview / experimental. plan.workflow.js is the autonomous-planning chain, invoked by /lets:plan-workflow via:
Workflow({ scriptPath: "${CLAUDE_PLUGIN_ROOT}/skills/plan-workflow/plan.workflow.js", args })
It runs the autonomous design without touching the heavily-used interactive /lets:plan. Once stable (after cross-project testing), the asset folds into native /lets:plan (as a --workflow mode or equivalent) and this standalone is retired (lets-jsw00).
Why this is autonomous-only (not a re-skin of review/opinion)
/lets:review --workflow and /lets:opinion --workflow are performance levers: same result, off-context. Native /lets:plan is interactive (clarify -> explore -> approaches -> architecture -> eval -> discuss); every checkpoint forces intermediate results back into context, which kills the off-context win. So the only workflow that pays off is the autonomous whole-command form: the user front-loads a RUBRIC, judge agents make the informed picks against it, and the run returns a plan + decision log. Steer-by-rubric + approve-at-end.
Stages (off-context, NO user gate between them)
- Explore - fan out
lets:explorerper focus area (EXPLORE_SCHEMA) -> codebase map. - Approaches - one
lets:architectsynthesizes 2-4 distinct approaches from the map + goal + rubric (APPROACHES_SCHEMA). - Architect - one
lets:architectper approach -> full architecture (ARCH_SCHEMA). - Judge - a panel (default
pragmatist, backend, security- neverarchitect) scores each architecture against the rubric and picks a winner (JUDGE_SCHEMA);aggregateJudgestallies winner-votes (tiebreak: summed totals) over REAL approach ids only. - Evaluate - expert panel evaluates the winner for risks (
EVAL_SCHEMA). - Plan - one
lets:architectwrites the bite-sized plan markdown, folding in eval findings (PLAN_SCHEMA). - Plan Review - fan out
lets:architect+lets:pragmatistover the WRITTEN plan (mirror/lets:review --plan,PLAN_REVIEW_SCHEMA) -> verdict + findings. - Revise - one
lets:architectapplies the review findings -> revised plan (REVISE_SCHEMA); skipped if no findings; planMd never lost on agent error. - Plan Check - one
lets:pragmatistruns a quick 5-lens sanity pass (mirror/lets:check --plan,PLAN_CHECK_SCHEMA) -> verdict + findings; catches regressions the revise introduced. - Refine - one
lets:architectapplies the check findings -> final plan; skipped if clean.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 66 lines · 51 tokens per session scan A 4b88d2114985
plan-workflow is a skill published in the GitHub repository restarter/lets-workflow (17 stars, last pushed 9d ago), licensed MIT. It adds 51 tokens to every session and 1,920 once invoked, about $0.0003 per session on Opus 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…