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/execute)<a href="https://agentmods.dev/commands/restarter/lets-workflow/execute"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/execute/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/execute"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/execute.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.00027 | $0.23265 |
| Opus 5.5 | $0.00011 | $0.09306 |
| Sonnet 5.5 | $0.00005 | $0.04653 |
| Haiku 4.5 | $0.00003 | $0.02327 |
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 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.
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 — 930 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 - inline, in Claude Code's native plan mode, or delegated: each commit-point chunk goes to a named implementer subagent, its diff is reviewed - by you or, under the gate policy you approve at Start, by the team's check - and corrections go back to that same agent. The plan provides the roadmap; the gates are plan mode (inline) or Step 5-D's Start, review and run-review gates (delegated).
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.
Another agent instead of this session: /lets:handoff --execute --send [<tab>] hands the plan to an agent tab of this worktree (Codex, Antigravity, Claude) as a self-contained brief; its commits come back UNVERIFIED for /lets:review --branch.
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 commit at each plan commit point through Skill(skill: "lets:commit", args: "approved=plan-files") 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.
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 · +2 lines d744dbf77569
- yesterday Changed 2d0a21172770
- 2d ago Changed · +2 lines 7e4b16279a32
- 3d ago Changed · -1 lines 24d555ca0243
- 15d ago Changed · +2 lines a61ffbdbe2ca
- 19d ago Changed · +4 lines 2a360f488271
- 20d ago Changed · +217 lines c817cdcc001c
- 23d ago Changed · +338 lines · +11 tokens per session 0b66b82ecae2
- 26d ago Changed · +2 lines 31e5486a5f14
- 28d ago First seen · 364 lines · 16 tokens per session scan C 46c06b01d2a9
execute is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 23,265 once invoked, about $0.0001 per session on Opus 5.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
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.