A command for adding progress notes, decisions, and context to the active coding task. It can also save a detailed resume note before the conversation is shortened.

Use it to record updates, decisions, context, or a recovery summary before compaction.

It keeps important task information available during longer work or when handing work back to a later session.

note — Command for Claude Code by restarter/lets-workflow

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.

Clone the repo

git clone --depth 1 https://github.com/restarter/lets-workflow

Made for: Claude Code.

Or install lets, the plugin that ships this one along with the rest of its 20 skills, 26 commands, 16 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/restarter/lets-workflow/note/github.svg)](https://agentmods.dev/commands/restarter/lets-workflow/note)

Your own site

<a href="https://agentmods.dev/commands/restarter/lets-workflow/note"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/note/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/restarter/lets-workflow/note"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/note.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 54 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,288 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00054	$0.02288
Opus 5.5	$0.00022	$0.00915
Sonnet 5.5	$0.00011	$0.00458
Haiku 4.5	$0.00005	$0.00229

Measured today against content hash 86487c5dbfc5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

plugins/lets/commands/note.md · 211 lines

How it starts

The opening of the file, as written. The whole thing — 211 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:commit records commits to the task
/lets:done documents task completion
/lets:end saves 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 --session        # RESUME snapshot of the whole session (aliases: --snapshot, --pre-compact, --compact)
/lets:note --team [text]    # team worktree: a decision -> the team file's Decisions, a fact -> its Standing knowledge

Step 0: Argument Parsing

If --session (aliases --snapshot, --pre-compact, --compact) is passed -> run Session Snapshot 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 --session. Then show the output below, NOT the generic Output box (no separate verify - the skill returns the path + task id, and /lets:end likewise just delegates and stops).

If --team is passed -> run Team Note Mode (below) INSTEAD of Steps 1-6: no task is needed and none is prompted for, no tracker verb runs. Then show its output, NOT the generic Output box.

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"

Read the full file on GitHub · 211 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.

today Changed · +20 lines · +14 tokens per session 86487c5dbfc5
19d ago Changed · +2 lines c025b4955f6c
28d ago Changed · +1 lines 9d83e4b1a425
1mo ago Changed · +3 lines · +12 tokens per session 56723d474b0b
1mo ago First seen · 185 lines · 28 tokens per session scan A e8b436e9dd1a

Subscribe to this mod's changes

note is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 2,288 once invoked, about $0.0002 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.

Claude Code Code review Planning ai-agents claude-code-plugin cli developer-tools

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.

starter-series/create-starter · 63 tokens

note

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Task Note

Usage

Step 0: Argument Parsing

When to Use

What this file has done since we first saw it

Other commands, from other repositories

audit-security

code-quality-plan-creator

mr-description-creator

agy-review

review

review-branch