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/reviewgit 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.00030 | $0.21955 |
| Opus 5 | $0.00015 | $0.10977 |
| Sonnet 5 | $0.00006 | $0.04391 |
| Haiku 4.5 | $0.00003 | $0.02195 |
Grade A, and why
review 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 — 1,451 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full Code Review
Comprehensive code review with dynamic agent selection based on change types. Up to 12 specialized agents, tiered severity scoring. Works with:
- GitHub and Bitbucket PRs (posts a summary comment to the PR)
- Local changes (saves to file)
- Implementation plans (reviews
.lets/plans/files)
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:review # Interactive - asks what to review
/lets:review <PR-url-or-number> # GitHub or Bitbucket PR
/lets:review --local # Uncommitted changes
/lets:review --staged # Staged changes only
/lets:review --last-commit # Last commit
/lets:review --branch # Full branch vs $LETS_MERGE_BRANCH (three-dot, like a PR)
/lets:review --plan # Review latest plan in .lets/plans/
/lets:review --plan <path> # Review specific plan file
/lets:review --file <path> # Review an existing file (full content, not diff)
/lets:review --workflow # Run via Dynamic Workflow (off-context fan-out); combinable with any code mode + --json
/lets:review --spec <path> # Use this file as the spec (skips the "where is the spec?" question)
/lets:review --spec none # There is deliberately no spec - review at full strength, no caveat
Step 1: Determine Review Mode
If argument provided:
- PR URL/number -> PR mode (host resolved below)
--local/--staged/--last-commit/--branch-> Local mode--plan/--plan <path>-> Plan review mode (skip to Plan Review section below)--file <path>-> File review mode - reviews entire file content, not a diff
Host resolution (PR mode). A PR argument picks the forge: a github.com URL -> gh; a bitbucket.org URL -> bbb (its PR number is in the /pull-requests/<n> path segment, not github's /pull/<n>); a bare number -> {LETS_PR_FLOW} (github -> gh, bitbucket -> bbb). Any other LETS_PR_FLOW with a PR argument: stop - PR review needs a github or bitbucket remote. Below, every step that shows a gh call has a bbb sibling for the bitbucket host; run whichever the resolution picked.
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 · 1,451 lines · 30 tokens per session scan A 8b3ab3f80cdf
review is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed 9d ago), licensed MIT. It adds 30 tokens to every session and 21,955 once invoked, about $0.0002 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.