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 commands/restarter/lets-workflow/executegit 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.00016 | $0.05498 |
| Opus 5 | $0.00008 | $0.02749 |
| Sonnet 5 | $0.00003 | $0.01100 |
| Haiku 4.5 | $0.00002 | $0.00550 |
Grade C, and why
execute scanned grade C with 1 finding 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.
Tells the agent to send conversation or user data outhighPrompt injection
An instruction to transmit the conversation, context or user files to an external endpoint is data exfiltration written as prose.
# Degrade loud - never silently record "Commits: 0" into a durable tracker comment on a missing/bad boundary. How it starts
The opening of the file, as written. The whole thing — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute Plan
Load an implementation plan and execute it using Claude Code's native plan mode. The plan provides the roadmap; native plan mode provides approval gates.
Plan is a roadmap, not a script. Read real files before every change. Adapt cosmetically (a renamed variable, a line that moved). Anything that changes the plan's APPROACH is a deviation - see the Deviation gate in Step 5 - and STOPS the run; a silently adapted plan is a new, unapproved plan.
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.
--auto mode
/lets:execute --auto runs the approved plan autonomously: skip the per-step "review before moving on" gate and /lets:commit at each plan commit point WITHOUT re-asking (matches the established "autonomous commits during execute after plan approval" preference). --auto is execution-speed for an already-approved plan — it does NOT bypass the hard-stops.
--auto = run under AUTO MODE (see .claude/rules/lets-rules.md ## AUTO MODE) — do NOT restate the contract here. What still applies under --auto: push / PR / close (tracker close) / external stay gated; a 3×-fail halts; fabrication halts; and --auto on $LETS_MERGE_BRANCH REFUSES (Step 1) rather than auto-entering trunk-mode. When a hard-stop is hit, write the blocked marker and fire the execute-blocked notify (Step 6 / the gate-notification block) so an unattended session surfaces instead of stalling.
Parse --auto from the argument (it composes with a plan path; it is mutually exclusive with --status).
Pipeline-state marker (under --auto)
A spawned autonomous session records its phase in a per-task marker file so N parallel worktrees don't clobber each other and the gate-notify (Step 6) can tell autonomous from interactive runs. Per-task filename (NOT a shared pipeline-state — .lets/ is a symlink shared across worktrees): .lets/cache/pipeline-state-<task-id>, single line <task-id>|<phase>|<iso>, phase ∈ planning | gate-clarify | gate-approve | executing | blocked | done. Write helper (run at each transition; only under --auto — interactive execute writes no marker, so it triggers no notify):
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 · 353 lines · 16 tokens per session scan C 4aecff07b5aa
execute is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed 9d ago), licensed MIT. It adds 16 tokens to every session and 5,498 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent to send conversation or user data out). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.