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/updategit 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.00055 | $0.02826 |
| Opus 5 | $0.00028 | $0.01413 |
| Sonnet 5 | $0.00011 | $0.00565 |
| Haiku 4.5 | $0.00006 | $0.00283 |
Grade C, and why
update scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- `NO_LETS_BINARY` → tell user: "`lets` binary not found on `$PATH`. Install it — `! curl -fsSL https://raw.githubusercontent.com/restarter/lets-workflow/main/scripts/install.sh | bash` (the leading `!` runs it in this s Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `NO_LETS_BINARY` → tell user: "`lets` binary not found on `$PATH`. Install it — `! curl -fsSL https://raw.githubusercontent.com/restarter/lets-workflow/main/scripts/install.sh | bash` (the leading `!` runs it in this s How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update LETS
Sync the drift-able LETS artifacts (four core + two optional: the user-scope global rules and the active tracker-<name>.md adapter) with the current release. Bridges to lets update --json (Go binary): auto-syncs .lets/.env (header refresh when LETS_ENV_VERSION is stale), .claude/rules/lets-rules.md (re-copy when outdated/missing - but deferred when the plugin is behind, so rules never sync to a stale plugin), and ~/.claude/rules/lets-rules.md (user-scope global rules - the user-rules row appears only when that file exists). It then computes a single ordered next_action (the self-driving loop): the binary step can be run in-session (approval-gated), the plugin step is a user-only Claude Code slash command, and a fully-synced machine prints ✓ Everything on vX.Y.Z.
MANDATORY: Execute every Step's bash block literally as written. Do not substitute output from earlier
ls/catin this conversation -.envand other dotfiles are invisible to plainls. Thetest -fchecks below ARE the contract.
Difference from /lets:init: /lets:init is first-time setup (it also asks config questions and sets up the statusline + beads). /lets:update only syncs what a new release changes - it never prompts and never touches settings.json or beads.
Step 1: Pre-checks
command -v lets >/dev/null 2>&1 || { echo "NO_LETS_BINARY"; exit 0; }
LETS_PROJECT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null) || { echo "NOT_GIT_REPO"; exit 0; }
test -f "$LETS_PROJECT_ROOT/.lets/.env" && echo "ENV_EXISTS" || echo "ENV_ABSENT"
Branch on output:
NO_LETS_BINARY→ tell user: "letsbinary not found on$PATH. Install it —! curl -fsSL https://raw.githubusercontent.com/restarter/lets-workflow/main/scripts/install.sh | bash(the leading!runs it in this session; or the same command without!in a terminal). See the README → Quick Start." NO LETS box. STOP.NOT_GIT_REPO→ tell user: "Not a git repository./lets:updateruns inside a LETS project." NO LETS box. STOP.ENV_ABSENT→ not initialized. Tell user: "This project hasn't been set up - run/lets:initfirst." Then still run Step 2 (it reports.env: not-initializedplus the binary/plugin status, which is useful). In Step 4 show the LETS box pointing at/lets:initinstead of/lets:start.ENV_EXISTS→ normal path. Continue to Step 2.
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 · 127 lines · 55 tokens per session scan C 743328181c5d
update is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed 9d ago), licensed MIT. It adds 55 tokens to every session and 2,826 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). 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.