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/start)<a href="https://agentmods.dev/commands/restarter/lets-workflow/start"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/start/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/start"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/start.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.00012 | $0.08830 |
| Opus 5.5 | $0.00005 | $0.03532 |
| Sonnet 5.5 | $0.00002 | $0.01766 |
| Haiku 4.5 | $0.00001 | $0.00883 |
Grade A, and why
start 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 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.
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 — 484 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Start
Restore context and prepare for work. User MUST select a task before working.
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.
LETS Notice — surface it. If a
## LETS Noticeblock is present in the injected context (a one-time message the SessionStart hook emits — e.g. workflow rules outdated/missing, a migration result), it MUST be the first line of your output for/lets:start(⚠️ <notice text>), before the session summary. Don't omit it — it tells the user a/lets:updateor/lets:initis needed. Mention it once, then continue with the steps below; don't repeat it in later turns.
Usage
/lets:start # Full flow - show history, tasks, select work
/lets:start <task-id> # Quick start - jump to specific task
/lets:start --continue # Resume last in_progress task with session context
/lets:start --main # Project-assistant / PM mode - no task, read + triage on merge-branch
/lets:start --assistant # Alias of --main
Step 0: Argument Parsing
Step 0a: Parse
Parse the arguments only - a task id (it goes through the detect-task id gate before any use), --continue, --main / --assistant, --scope "<text>" (main mode: the part of the repo this orchestrator owns). --orc is stripped per the detect-task explicit-argument convention before the task-id test and forwarded to take-task; with --main it is dropped with a one-line note (an orchestrator is never bound). No tracker verb runs here. Every path below runs Step 0.5 first, then its own steps.
--orc without a task id (not --main - e.g. the lead /lets:team create launched with '/lets:start --orc="<name>"'): after Step 0.5, record the binding on the current branch right away, single-quoting the name ('\'' for a quote inside it) - the same call detect-task uses for an in-progress task:
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 · +22 lines d915abadc8f6
- 2d ago Changed 24e99bbc6c69
- 3d ago Changed · +8 lines fed9e37e97b5
- 15d ago Changed · +4 lines 96731df73856
- 19d ago Changed · +2 lines 6e4913bbe071
- 20d ago Changed · +18 lines 2c3643978802
- 22d ago Changed fb8a3c6fd459
- 23d ago Changed 7be5edfab394
- 24d ago Changed · +17 lines a8cec54d8cc8
- 26d ago First seen · 413 lines · 12 tokens per session scan A ddf184829b39
start is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 8,830 once invoked, about $0.0000 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.