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-implement)<a href="https://agentmods.dev/commands/leanandmean/scramjet/mach12-issue-implement"><img src="https://agentmods.dev/badge/commands/leanandmean/scramjet/mach12-issue-implement/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-issue-implement"><img src="https://agentmods.dev/badge/commands/leanandmean/scramjet/mach12-issue-implement.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.03473 |
| Opus 5.5 | $0.00004 | $0.01389 |
| Sonnet 5.5 | $0.00002 | $0.00695 |
| Haiku 4.5 | $0.00001 | $0.00347 |
Grade A, and why
mach12:issue-implement 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 1mo 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Stage
Goals
- Complete exactly the requested implementation-plan stage or range with the smallest sound change that preserves the issue's requirements and approved architecture.
- Leave the requested scope's intended files verified, committed, pushed, and documented in a durable progress artifact.
- Report remaining work accurately and offer only the next planned stage or PR creation when its prerequisites are satisfied.
Step 1: Parse Input
The user's input typically contains:
- An issue number (required)
- A stage number or range (required)
- Additional context or constraints (optional)
Example inputs:
55 155 2 but only the frontend parts55 stages 3-4
Extract the issue number and stage(s). If the input is ambiguous, ask the user to clarify.
Step 2: Ensure Feature Branch
Before gathering context or doing any work, ensure you are on an appropriate feature branch. Implementation must never happen directly on the default branch.
Determine the current branch and the default branch:
git branch --show-current
gh repo view --json defaultBranchRef --jq .defaultBranchRef.name
If on the default branch
-
Check for uncommitted changes with
git status --porcelain. If the working tree is dirty, stop and tell the user to commit or stash their changes before proceeding. -
Search for convention-named branches that match the issue number. Run
git branch -aand normalize each result by trimming leading whitespace and stripping theremotes/origin/prefix if present. Then filter for branches that start withfeature/issue-<number>-orfix/issue-<number>-, or that equalfeature/issue-<number>orfix/issue-<number>exactly. Use strict matching so thatissue-4-does not matchissue-42-. -
Exactly one match found: Check it out with
git checkout <branch>andgit pull --ff-only. If the pull fails because local and remote have diverged, stop and tell the user to resolve the divergence before continuing.
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.
- 1mo ago Changed e8cc73f4ef76
- 1mo ago Changed · +12 lines d42e0583c523
- 1mo ago First seen · 177 lines · 10 tokens per session scan A 15193c622306
mach12:issue-implement is a command published in the GitHub repository LeanAndMean/scramjet (8 stars, last pushed 10d ago), licensed Apache-2.0. It adds 10 tokens to every session and 3,473 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-31.
Other commands, from other repositories
afcl
Close feature [agent] [--adopt] - merges branch, cleans up, optionally adopts from losers (shortcut for feature-close).
next
Suggest the most likely next workflow action based on current context.
aft
Transfer feature from its current agent to a different agent — preserves commits and in-flight work (shortcut for feature-transfer).
aigon-feature-transfer
Hand a stuck or paywalled in-progress feature from its current agent to a different agent, without losing commits or in-flight work. Intended for.
afs
Start feature [agents...] - create workspace and begin implementation (shortcut for feature-start).
afo
Open feature worktree in terminal and start agent (shortcut for feature-open).