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/statuslinegit 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.00018 | $0.01042 |
| Opus 5 | $0.00009 | $0.00521 |
| Sonnet 5 | $0.00004 | $0.00208 |
| Haiku 4.5 | $0.00002 | $0.00104 |
Grade A, and why
statusline 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 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.
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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Statusline Appearance
Thin dispatcher for the statusline's persisted appearance. All file work lives in the Go subcommand lets statusline config (cli/internal/statuslinecmd/); this command captures intent via AskUserQuestion, shells out with --json, and renders the result.
The choice is written to .claude/settings.local.json (personal, gitignored) - NOT the tracked .claude/settings.json - so your --light/--compact preference never gets forced onto collaborators. A changed statusLine command is re-read by Claude Code only on session start - tell the user to restart.
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.
Step 0: Parse Argument
| Argument | Action |
|---|---|
show |
go to Show (read-only, no prompt) |
reset |
go to Reset (persist defaults) |
| (none) / anything else | go to Configure (interactive) |
Show
lets statusline config --show --json
Parse the envelope and report the current appearance in one line (palette + which rows are hidden + compact), plus the settings_path. Then stop (render the Output line).
Reset
lets statusline config --reset --json
Parse the envelope; on ok=true confirm "reset to defaults". Add the restart note. Render the Output line.
Configure
Step C1: Load current state
lets statusline config --show --json
Parse appearance (light, compact, no_tip, no_dir, no_task) from the envelope. Use it to tell the user what's currently set (the prompts below select the absolute desired state, not a delta). If the envelope is ok=false with error.kind == "foreign_statusline", the local file has a custom statusLine - surface error.message and ask whether to overwrite it (if yes, add --force to the apply in Step C3); otherwise stop.
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 · 111 lines · 18 tokens per session scan A 1ea378020565
statusline is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed 9d ago), licensed MIT. It adds 18 tokens to every session and 1,042 once invoked, about $0.0001 per session on Opus 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
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.