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/leanandmean/mach10/pr-reviewgit clone --depth 1 https://github.com/LeanAndMean/mach10Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/leanandmean/mach10/pr-review)<a href="https://agentmods.dev/commands/leanandmean/mach10/pr-review"><img src="https://agentmods.dev/badge/commands/leanandmean/mach10/pr-review.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00014 | $0.04329 |
| Opus 5 | $0.00007 | $0.02165 |
| Sonnet 5 | $0.00003 | $0.00866 |
| Haiku 4.5 | $0.00001 | $0.00433 |
Grade A, and why
pr-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 5d 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 — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review PR
You are running a comprehensive review of a pull request, posting the results, then independently assessing each finding to separate genuine issues from nitpicks and false positives.
User input: $ARGUMENTS
Note: This command performs best with an Opus-class model. On Sonnet or Haiku, results may be shallower.
Step 0: Parse input and create task list
The user's input typically contains:
- A PR number (required)
- Additional context, focus areas, or constraints (optional)
Example inputs:
108108 error handling and test coverage108 focus on the new API endpoints
Extract the PR number. If context was provided, note it for Step 2. If the input is ambiguous, ask the user to clarify.
After parsing input, create the progress-tracking task list. Create a task for Step 0 and immediately mark it in progress. Then create tasks for each of the remaining 8 steps one at a time, in step order, all starting as pending. Task list display order matches creation order, so each task must be a separate sequential call -- do not batch multiple task creations in a single message. Store each returned task ID for later use -- do not assume IDs are sequential.
| Task | Subject | activeForm |
|---|---|---|
| Step 0 | Step 0: Parse input and create task list | Parsing input |
| Step 1 | Step 1: Check out PR branch | Checking out PR branch |
| Step 2 | Step 2: Delegate PR review to pr-review-toolkit | Delegating PR review |
| Step 3 | Step 3: Post review comment | Posting review comment |
| Step 4 | Step 4: Run independent assessment | Running independent assessment |
| Step 5 | Step 5: Post assessment comment | Posting assessment |
| Step 6 | Step 6: Present CLI summary | Presenting summary |
| Step 7 | Step 7: Handle deferred items | Handling deferred items |
| Step 8 | Step 8: Recommend next steps | Recommending next steps |
Mark Step 0 complete.
Step 1: Check out PR branch
Mark Step 1 in progress.
Ensure you are on the correct branch:
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.
- 5d ago First seen · 334 lines · 14 tokens per session scan A ccb6a2c1821f
pr-review is a command published in the GitHub repository LeanAndMean/mach10 (20 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 4,329 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
doctor
Health check for greatcto. Shows pipeline state, missing artefacts, hook status, last run per agent, and permission-denied tail.
review
12-angle code review + skeptical triage (3-round + arbiter) for security/reliability P0/P1 findings, OR traceability tree. Default: review current branch vs main. --deep: triage ALL P0/P1 angles (not just security). With trace : render REQ → IMPL → TEST tree for impact analysis. Creates or closes gate:code for…
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
discover
Run a full product discovery cycle — from outcome definition through opportunity mapping, prioritisation, and experiment design. Use when the team isn't sure what to build next, or before writing a PRD for a complex feature space.
resume
Resume a previous session. Reads recent session logs, open tasks, and last decisions — gives Claude full context without re-explaining the project.
ccr
CCR (Compressed Context with Retrieval) — recall the full original of context that greatcto compressed/filtered out, by its short id. The retrieval half of the compression layer.