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-issue-review)<a href="https://agentmods.dev/commands/leanandmean/scramjet/mach12-issue-review"><img src="https://agentmods.dev/badge/commands/leanandmean/scramjet/mach12-issue-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.1 | $0.00017 | $0.05688 |
| Opus 5 | $0.00009 | $0.02844 |
| Sonnet 5 | $0.00003 | $0.01138 |
| Haiku 4.5 | $0.00002 | $0.00569 |
Grade A, and why
mach12:issue-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 3d 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Plan Review
Goals
- Independently determine whether the current implementation plan is correct, complete, minimal, testable, and executable from the issue's authoritative context.
- Give every finding an evidence-grounded classification and preserve one aggregate judgment across command and runtime responsibilities.
- Leave a verified replacement plan or required decision record when the user chooses one, and route implementation only after the applicable publication gate passes.
Step 1: Parse input
The user's input contains:
- An issue number (required)
- Additional context or constraints (optional)
Extract the issue number from the input. If the input is ambiguous, ask the user to clarify. If context was provided, note it for use during exploration and review.
Step 2: Read the issue and locate the plan
Delegate to:
/mach12:gh-issue-read <issue-number> --marker mach12-plan
The subroutine returns the issue title, body, full comments stream, and the body of the comment tagged with <!-- mach12-plan --> (using the last match if multiple exist).
Understand:
- The original problem statement and requirements.
- The implementation plan (typically posted as a comment).
- Any discussion, decisions, or clarifications in the comment thread.
If the marker comment was not found, fall back to identifying the most recent substantive comment that contains a staged implementation plan in the returned comments stream. If no plan exists at all, inform the user and suggest running /mach12:issue-plan <issue-number> first, then stop.
Step 3: Read contribution guidelines
Delegate to:
/mach12:find-contribution-guidelines
The subroutine returns any planning-relevant guidance found in CONTRIBUTING.md, DEVELOPMENT.md, or .github/CONTRIBUTING.md: expected project layers, testing expectations, documented development tools, and any other requirements that a complete plan should satisfy.
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.
- 3d ago Changed · +19 lines b6149885f12d
- 8d ago First seen · 249 lines · 17 tokens per session scan A d14be962b6de
mach12:issue-review is a command published in the GitHub repository LeanAndMean/scramjet (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 17 tokens to every session and 5,688 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
computer
Drive a computer's screen, mouse, and keyboard.
find-issues
Find GitHub issues that a PR might fix.
afr
Review feature - code review with fixes by a different agent (shortcut for feature-code-review).
afrv
Revise the current feature worktree after code review — decide accept/revert/modify (shortcut for feature-code-revise).
afe
Evaluate feature - code review or comparison (shortcut for feature-eval).
find-duplicate-prs
Find open PRs that may duplicate a given PR.