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-pre-merge)<a href="https://agentmods.dev/commands/leanandmean/mach10/pr-pre-merge"><img src="https://agentmods.dev/badge/commands/leanandmean/mach10/pr-pre-merge.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.1 | $0.00017 | $0.02468 |
| Opus 5 | $0.00009 | $0.01234 |
| Sonnet 5 | $0.00003 | $0.00494 |
| Haiku 4.5 | $0.00002 | $0.00247 |
Grade A, and why
pr-pre-merge 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 7d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Merge Checklist
You are running the pre-merge checklist for a PR that has passed review. Walk through each checklist item, perform the necessary updates, and commit the results.
User input: $ARGUMENTS
Step 0: Parse input and create task list
The user's input contains:
- A PR number (required)
- Additional context or constraints (optional)
Extract the PR number from the input. If the input is ambiguous, ask the user to clarify. If context was provided, note it for use in Step 5.
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 7 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: Read contributing guidelines | Reading contributing guidelines |
| Step 2 | Step 2: Check out and prepare | Checking out PR branch |
| Step 3 | Step 3: Check branch freshness | Checking branch freshness |
| Step 4 | Step 4: Gather PR context | Gathering PR context |
| Step 5 | Step 5: Run pre-merge checklist | Running pre-merge checklist |
| Step 6 | Step 6: Commit checklist changes | Committing checklist changes |
| Step 7 | Step 7: Present pre-merge report | Presenting report |
Mark Step 0 complete.
Step 1: Read contributing guidelines
Mark Step 1 in progress.
Look for project contribution guidelines in order of precedence:
CONTRIBUTING.md
DEVELOPMENT.md
.github/CONTRIBUTING.md
Read only the first file found; skip the rest.
If found, read the file and extract any pre-merge requirements (version bumps, changelog entries, documentation updates, test requirements, etc.).
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.
- 7d ago First seen · 220 lines · 17 tokens per session scan A 7e272fc2db15
pr-pre-merge is a command published in the GitHub repository LeanAndMean/mach10 (20 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 2,468 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
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.
save
Save current session. Writes a session log with what was done, decisions made, and what's pending. Optional: commit & push.
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…
audit
Audit an existing codebase. Detects stack, finds gaps, creates tasks, generates PROJECT.md.
migrate
Migrate existing PROJECT.md to the latest greatcto schema — appends missing fields without touching existing values.