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/scramjetWrote 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/scramjet/mach12-pr-pre-merge)<a href="https://agentmods.dev/commands/leanandmean/scramjet/mach12-pr-pre-merge"><img src="https://agentmods.dev/badge/commands/leanandmean/scramjet/mach12-pr-pre-merge/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/scramjet/mach12-pr-pre-merge"><img src="https://agentmods.dev/badge/commands/leanandmean/scramjet/mach12-pr-pre-merge.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.00020 | $0.04419 |
| Opus 5 | $0.00010 | $0.02210 |
| Sonnet 5 | $0.00004 | $0.00884 |
| Haiku 4.5 | $0.00002 | $0.00442 |
Grade A, and why
mach12: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 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Merge Checklist
Goals
- Bring the pull-request branch to a current state with applicable policy, test, and CI outcomes authoritatively recorded, including user-authorized skips.
- Complete and publish any required documentation, version, changelog, conflict-resolution, or CI-fix changes without absorbing unrelated work.
- Report a determinate readiness result and offer merge only when every required gate succeeds.
Step 1: Parse input
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 7.
Step 2: Verify initial readiness
Read ordinary GitHub readiness before changing the branch:
gh pr view <pr-number> --json state,isDraft,reviewDecision,mergeable,mergeStateStatus
Require the PR to be open, non-draft, and free of requested changes or required review, and read required checks with gh pr checks <pr-number> --required. If GitHub reports CONFLICTING or DIRTY, retain that conflict evidence and continue through checkout to Step 4 for guarded remediation rather than blocking immediately. This route does not bypass Step 4's Merge/Cancel choice and does not authorize an automatic merge. A behind branch continues to Step 4, and pending or failing checks continue to Step 9 for resolution rather than blocking the checklist immediately. If GitHub still reports mergeability as unknown after one brief reread, report incomplete rather than guessing.
No creator, provenance marker, issue linkage, or custom metadata participates in readiness.
Step 3: Check out and prepare
Check out the PR branch:
gh pr checkout <pr-number>
If checkout fails, report the error to the user and stop.
Synchronize the checked-out branch:
git pull
If the pull fails due to authentication, network error, or merge conflicts, report the error and stop -- the checklist cannot proceed without a clean, up-to-date working copy.
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 Changed · +6 lines 8cd9872adcf1
- 10d ago First seen · 301 lines · 20 tokens per session scan A 9d0878d3d658
mach12:pr-pre-merge is a command published in the GitHub repository LeanAndMean/scramjet (7 stars, last pushed today), licensed Apache-2.0. It adds 20 tokens to every session and 4,419 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-31.
Other commands, from other repositories
aft
Transfer feature from its current agent to a different agent — preserves commits and in-flight work (shortcut for feature-transfer).
afs
Start feature [agents...] - create workspace and begin implementation (shortcut for feature-start).
afsrv
Revise feature spec after pending spec reviews — decide and acknowledge in one pass (shortcut for feature-spec-revise).
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
afo
Open feature worktree in terminal and start agent (shortcut for feature-open).
research-spec-revise
Revise research spec after pending spec reviews — decide and acknowledge in one pass.