status

A read-only command that shows your current project position, active work, and next items. It is part of the lets task-tracking system.

In plain words
What is it for?
Checking what is in progress, what should happen next, and which follow-up command fits the current project state.
Why use it?
It gives a quick orientation without changing tasks, opening menus, or starting agents.

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/status
Clone the repo
git clone --depth 1 https://github.com/restarter/lets-workflow
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 320 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.00020 $0.00320
Opus 5 $0.00010 $0.00160
Sonnet 5 $0.00004 $0.00064
Haiku 4.5 $0.00002 $0.00032

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

Security

Grade A, and why

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

plugins/lets/commands/status.md · 28 lines

What it actually says

Status

A fast, read-only orientation: where you are, what's in flight, what's next. No menu, no dialog, no mutation, no agents. Argless.

For working the backlog (pulse / ideas / cleanup) use /lets:backlog. To claim a task and start, /lets:start.

Step 1: Render the snapshot

Invoke Skill(skill: "lets:orient") - it renders ## Where you are / ## In flight / ## Next up (and ## Project counts when the tracker provides them), degrading per tracker (beads | none | a custom adapter).

If a legacy view argument was passed (overview / ready / labels / blocked / full), ignore it and note once: "Status is now a single orient snapshot; the old views were removed. Deeper dashboards, where a tracker offers them, live in that tracker's own native tooling."

State-driven Nav (per .claude/rules/lets-rules.md ### Response Footer):

  • Uncommitted changes on disk -> /lets:commit.
  • Active task, clean tree -> /lets:note + /lets:check.
  • No active task -> /lets:start.

Rules

  • Read-only - never mutate or claim from here.
  • Respond in the user's language.
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 · 28 lines · 20 tokens per session scan A 59f4c5f0ecd3

Subscribe to this mod's changes

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