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/notegit 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.00028 | $0.01603 |
| Opus 5 | $0.00014 | $0.00801 |
| Sonnet 5 | $0.00006 | $0.00321 |
| Haiku 4.5 | $0.00003 | $0.00160 |
Grade A, and why
note 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Note
Add a note to the active task. For mid-work documentation - progress updates, research findings, decisions, context for future sessions.
This is a utility, not a flow step. Main flow handles documentation automatically:
/lets:commitrecords commits to the task/lets:donedocuments task completion/lets:endsaves session progress
Use /lets:note when you want to add extra context that doesn't fit those flows.
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.
Usage
/lets:note # interactive - pick a note type, add to the active task
/lets:note <free text> # use the text directly as the note (infer type)
/lets:note --pre-compact # RESUME snapshot of the whole session before /compact
Step 0: Argument Parsing
If --pre-compact (alias --compact) is passed -> run Pre-Compact Resume Mode (below) INSTEAD of Steps 3-4: no type prompt, produce ONE recovery-grade snapshot. Do NOT run Step 1's interactive task prompt - the session-snapshot skill owns task detection (file-primary: ambiguity -> file only, no prompt), keeping this byte-identical to /lets:end --pre-compact. Then show the Pre-Compact output below, NOT the generic Output box (no separate verify - the skill returns the path + task id, and /lets:end --pre-compact likewise just delegates and stops).
Otherwise -> normal flow (Steps 1-6).
When to Use
- Research findings: "Investigated X, found Y"
- Design decisions: "Chose approach A because..."
- Blocker discovered: "Can't proceed until Z"
- Context dump: "Important info for next session"
Step 1: Active Task Detection
Use the detect-task skill to find the active task: Skill(skill: "lets:detect-task").
If no active task or multiple tasks found - ask user which task to add a note to.
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 · 185 lines · 28 tokens per session scan A e8b436e9dd1a
note is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed 9d ago), licensed MIT. It adds 28 tokens to every session and 1,603 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.