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.
git 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-fix)<a href="https://agentmods.dev/commands/leanandmean/mach10/pr-review-fix"><img src="https://agentmods.dev/badge/commands/leanandmean/mach10/pr-review-fix/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/leanandmean/mach10/pr-review-fix"><img src="https://agentmods.dev/badge/commands/leanandmean/mach10/pr-review-fix.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00010 | $0.01625 |
| Opus 5.5 | $0.00004 | $0.00650 |
| Sonnet 5.5 | $0.00002 | $0.00325 |
| Haiku 4.5 | $0.00001 | $0.00162 |
Grade A, and why
pr-review-fix 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 2mo 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Review Issues
You are fixing specific issues identified in a PR review. This command gathers context from the PR and its review comments, then delegates to the feature-dev workflow for implementation.
User input: $ARGUMENTS
Step 0: Parse input and create task list
The user's input typically contains:
- A PR number (required)
--review-comment <id>flag with a numeric comment ID (optional)--assessment-comment <id>flag with a numeric comment ID (optional)- Finding identifiers to fix -- space-separated F/S identifiers (e.g.,
F1 F2 S3) or bare numbers as fallback (optional) - Additional context or constraints (optional)
Example inputs:
108(PR only -- read the PR and determine which review findings to fix)108 F1 F2 S3108 --review-comment 1234567890 --assessment-comment 1234567891 F1 F2 S3108 --review-comment 1234567890 F1 S2 focus on error handling
Extract the PR number. Parse --review-comment and --assessment-comment flags if present (each followed by a numeric ID). If finding identifiers are provided (F/S prefixed or bare numbers), note them. 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 4 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: Gather PR and review context | Gathering context |
| Step 2 | Step 2: Identify issues to fix | Identifying issues |
| Step 3 | Step 3: Delegate review fixes to feature-dev | Delegating review fixes to feature-dev |
| Step 4 | Step 4: Recommend next steps | Recommending next steps |
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.
- 2mo ago First seen · 143 lines · 10 tokens per session scan A aeeab344805a
pr-review-fix is a command published in the GitHub repository LeanAndMean/mach10 (23 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 1,625 once invoked, about $0.0000 per session on Opus 5.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
crystallize
After a session or an incident, turn what happened into reusable knowledge — learn captures this session's lessons, review/approve promotes incident patterns into agent improvements, skill turns a repeating procedure into a skill.
poc
Before building on an unproven idea, get a timeboxed yes/no answer — start a hypothesis-driven POC that skips 80% of the production pipeline and forces ship/pivot/kill at expiry, then promote a shipped POC through the audits it skipped.
sec
Security umbrella: posture metrics, threat model, SBOM, incident workflow. Subcommands: status (default) | threat | sbom | incident | rotate.
ownership
When you need to know who owns a path and who answers for it — the service ownership matrix (team, lead, on-call, SLA) auto-detected from git with CODEOWNERS generated, plus on-call rotations, shift handoffs and escalation paths.
rfc
RFC process for cross-team decisions. Create, track, and close RFCs. Accepted RFCs auto-create ADRs.
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.