backlog

A backlog-management command with review, quick pulse, and cleanup modes. A backlog is the list of unfinished work, and triage means deciding what should happen to each item.

In plain words
What is it for?
Use it for a fast backlog check, a broader multi-agent review, or interactive cleanup of backlog items.
Why use it?
It helps turn a large or stale work list into clearer decisions about what to keep, remove, or address next.

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/backlog
Clone the repo
git clone --depth 1 https://github.com/restarter/lets-workflow
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,446 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.00023 $0.06446
Opus 5 $0.00012 $0.03223
Sonnet 5 $0.00005 $0.01289
Haiku 4.5 $0.00002 $0.00645

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

Security

Grade A, and why

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

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/backlog.md · 649 lines

How it starts

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

Backlog

Backlog management in three modes. Review (heavy) launches an explorer + parallel domain agents for multi-perspective backlog insights. --fast is a quick no-agent backlog pulse (orchestrator-only, the lightweight sibling of Review). Cleanup is fast interactive triage - no agents.

Quick no-agent backlog pulse: /lets:backlog --fast. For HOW to build something, use /lets:plan. For an open question or decision about the project, use /lets:opinion.

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:backlog            # Ask which mode, then go
/lets:backlog review     # Multi-agent backlog review (skip menu)
/lets:backlog cleanup    # Interactive triage cleanup (skip menu)
/lets:backlog review --workflow  # Run the Review fan-out + aggregate off-context via a Dynamic Workflow

Step 0: Choose Mode

Parse the argument first: strip a --fast token (sets fast mode - no agents) and a --workflow token (sets workflow mode - Review only) if present; the remaining token is the mode keyword. Precedence/compat:

  • --fast selects the orchestrator-only Fast mode (a quick no-agent pulse) regardless of the review/no-arg keyword. --fast + --workflow -> --fast wins (orchestrator-only beats off-context fan-out); note it in one line.
  • --fast passed with cleanup is ignored with a one-line note (Cleanup is already no-agent triage).
  • --workflow passed with cleanup is ignored with a one-line note (Cleanup has no agents).

If an argument is provided, parse it: --fast -> Fast mode (below); review -> Review Backlog Mode; cleanup -> Cleanup Mode. A remaining token that is neither review nor cleanup is an area/topic filter -> Fast mode with that token as the F1 filter (e.g. /lets:backlog --fast auth scopes the pulse to auth; a bare /lets:backlog <area> implies Fast mode too).

Read the full file on GitHub · 649 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. yesterday First seen · 649 lines · 23 tokens per session scan A aa19129e2ac1

Subscribe to this mod's changes

backlog is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed 9d ago), licensed MIT. It adds 23 tokens to every session and 6,446 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.