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/checkgit 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.00017 | $0.06981 |
| Opus 5 | $0.00009 | $0.03490 |
| Sonnet 5 | $0.00003 | $0.01396 |
| Haiku 4.5 | $0.00002 | $0.00698 |
Grade A, and why
check 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.
How it starts
The opening of the file, as written. The whole thing — 465 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Local Code Check
Fast inline sanity check from 6 perspectives. Same target selection as /lets:review - the difference is depth: /lets:check reviews inline (no subagent dispatch, no AskUserQuestion gates), /lets:review dispatches expert agents.
Usage
/lets:check # uncommitted changes (default, same as --local)
/lets:check --local # uncommitted changes (explicit)
/lets:check --staged # only staged changes
/lets:check --last-commit # last commit
/lets:check --branch # full branch vs $LETS_MERGE_BRANCH (three-dot, like a PR)
/lets:check <PR-url-or-number> # quick PR sanity (gh pr diff, inline - no agents)
/lets:check --file <path> # quick sanity of an existing file (full content, not a diff)
/lets:check --plan # quick plan sanity check
/lets:check --plan <path> # quick sanity of a specific plan file
/lets:check ... --json # structured JSON output instead of console report
/lets:check --spec <path> # use this file as the spec (or a bare task id)
/lets:check --spec none # there is deliberately no spec - no spec block, no caveat
When to Use
- Quick sanity check during development
- Before commit for significant changes
- When unsure if code is ready
- Spot check after refactoring
- Fast first pass on a PR before a full
/lets:review
For full review: Use /lets:review (same modes, multiple expert agents, deeper analysis). Every mode below has a /lets:review --<same-flag> upgrade path.
Step 0: Determine Mode
Parse the argument(s):
| Argument | Mode | Target |
|---|---|---|
--plan / --plan <path> |
Plan review | go to Plan Mode section below, skip code steps |
--file <path> |
File review | entire file content (not a diff) |
| bare PR URL or number (not a flag) | PR | gh pr diff <PR> |
--local / no argument |
Local (default) | git diff (uncommitted) |
--staged |
Local | git diff --staged |
--last-commit |
Local | git diff HEAD~1 |
--branch |
Local | three-dot merge-base diff against the base the Step 1 guard resolves (origin/{LETS_MERGE_BRANCH} when it exists) |
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.
- yesterday First seen · 465 lines · 17 tokens per session scan A 6de93feb8452
check is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed 9d ago), licensed MIT. It adds 17 tokens to every session and 6,981 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.