init

A project setup command for LETS, which creates the files and configuration needed to use LETS in the current project. It checks whether the folder is a Git repository and whether setup has already been run.

In plain words
What is it for?
Use it when starting LETS in a project, creating its project structure and configuration, and setting up related status and issue-tracking files.
Why use it?
It removes the manual work of preparing a project and can distinguish a first setup from a repeat run.

Command

Install

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.

agentmods
npx agentmods add commands/restarter/lets-workflow/init
Clone the repo
git clone --depth 1 https://github.com/restarter/lets-workflow
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,653 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00035 $0.05653
Opus 5 $0.00017 $0.02826
Sonnet 5 $0.00007 $0.01131
Haiku 4.5 $0.00003 $0.00565

Measured 2d ago against content hash ba0f0fad1799, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

init 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 se

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 se
plugins/lets/commands/init.md · 416 lines

How it starts

The opening of the file, as written. The whole thing — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project Initialization

Per-project LETS setup. Bridges to lets init --json (Go binary) for all filesystem mutation. Slash command captures user prefs via AskUserQuestion, exec's the binary, parses JSON stdout, renders to user.

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.

MANDATORY: Execute every Step's bash block literally as written. Do not substitute output from earlier ls/cat/bd show in this conversation — .env and other dotfiles are invisible to plain ls. The test -f / test -d checks below ARE the contract for branching first-time-vs-re-run paths; shortcutting them produces wrong branches.

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"
if [ -n "$LETS_PROJECT_ROOT" ]; then
  test -f "$LETS_PROJECT_ROOT/.lets/.env" && echo "ENV_EXISTS" || echo "ENV_ABSENT"
  test -d "$LETS_PROJECT_ROOT/.beads" && echo "BEADS_EXISTS" || echo "BEADS_ABSENT"
fi

Branch on output:

  • 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 session; or the same command without ! in a terminal). See the README → Quick Start." NO LETS box. STOP.
  • NOT_GIT_REPO → ask user via AskUserQuestion (Step 1a below). If user picks "Init git" → run git init, recompute LETS_PROJECT_ROOT, ENV_ABSENT/BEADS_ABSENT (both will be absent for fresh repo). If "Cancel" → stop, NO LETS box.
  • ENV_ABSENT → first-time path (Step 2). Use BEADS_ABSENT/BEADS_EXISTS to decide whether to ask about beads init in Step 2c-bis.
  • ENV_EXISTS → re-run path (Step 3). Don't re-ask about beads — lets init self-heals (StepSkip if already inited; StepWarn if bd not on PATH).

Read the full file on GitHub · 416 lines

Changes

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.

  1. 2d ago First seen · 416 lines · 35 tokens per session scan C ba0f0fad1799

Subscribe to this mod's changes

init is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed 9d ago), licensed MIT. It adds 35 tokens to every session and 5,653 once invoked, about $0.0002 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.