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/github-prgit 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.00020 | $0.10466 |
| Opus 5 | $0.00010 | $0.05233 |
| Sonnet 5 | $0.00004 | $0.02093 |
| Haiku 4.5 | $0.00002 | $0.01047 |
Grade C, and why
github-pr scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
1. Delete PR folder: `rm -rf "$PR_DIR"` (removes state + all temp files) How it starts
The opening of the file, as written. The whole thing — 1,226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub PR Review Lifecycle
Full GitHub PR review lifecycle: analyze code, discuss findings with user, post inline comments, follow-up on fixes, approve or request changes.
GitHub only (the full posting lifecycle). This command drives inline comments / follow-up / approve / merge exclusively via the gh CLI. For Bitbucket, /lets:review <PR> already reviews a PR end to end (fetch + diff + discussion + summary post via bbb); only the inline/approve/merge lifecycle here stays GitHub-only for now. LETS_PR_FLOW=local users finish tasks via /lets:done.
Requires: gh CLI installed and authenticated.
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:github-pr <PR-url-or-number> # Start new review
/lets:github-pr # Resume from saved state
/lets:github-pr --follow-up # Check if fixes addressed comments
/lets:github-pr --respond [PR] # Author: triage review comments, fix, reply
/lets:github-pr --approve # Approve PR
/lets:github-pr --merge # Merge PR
/lets:github-pr --status # Show current review state
/lets:github-pr --cancel # Clean up state, abandon review
Step 1: Detect Mode
Verify gh CLI
gh auth status 2>&1 || echo "gh not authenticated"
If gh not available or not authenticated, stop: "gh CLI required. Run gh auth login."
Parse argument
Interpret user intent:
- PR URL or number -> extract PR number
--follow-up-> Phase 3--respond-> Phase R (author respond)--approve-> Phase 4--merge-> merge only--status-> show state and exit--cancel-> clean up state and exit- No argument, no flag -> check for existing state files
Check for existing state
LETS_PROJECT_ROOT=$(git rev-parse --show-toplevel)
PR_DIR="$LETS_PROJECT_ROOT/.lets/execution/pr-{number}"
STATE_FILE="$PR_DIR/review.json"
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,226 lines · 20 tokens per session scan C 5429a77e2668
github-pr 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 10,466 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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.