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.
npx agentmods add commands/leanandmean/scramjet/mach12-pr-creategit 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-create)<a href="https://agentmods.dev/commands/leanandmean/scramjet/mach12-pr-create"><img src="https://agentmods.dev/badge/commands/leanandmean/scramjet/mach12-pr-create.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 | $0.00011 | $0.01523 |
| Opus 5 | $0.00005 | $0.00762 |
| Sonnet 5 | $0.00002 | $0.00305 |
| Haiku 4.5 | $0.00001 | $0.00152 |
Grade A, and why
mach12:pr-create 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 4d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request
You are creating a pull request for the current branch, with a structured description that includes a summary, test plan, and optional issue linkage.
Step 1: Parse input and resolve linkage
The user may provide an issue number, an issue number plus context, context alone, or nothing.
Resolve issue-linkage ambiguity before constructing a draft:
- An explicit canonical positive issue number is the proposed linked issue.
- If user input could be either an issue number or general context, ask which interpretation is intended.
- If multiple plausible issue candidates exist in the input or branch name, present them and ask the user to select exactly one issue or explicitly decline linkage.
- Do not resolve ambiguity by silently producing an unlinked draft or by deferring the decision to draft approval.
- If no issue was supplied and exactly one issue is unambiguously encoded by a branch pattern such as
feature/issue-55-*,fix/issue-55-*, or55-some-description, use that issue. - If no issue was supplied and the branch yields no candidate, proceed unlinked.
When one issue is selected, delegate to /mach12:gh-issue-read <issue-number>. If the read fails, report the error and stop. Issue comments may inform the summary and test plan but must not be copied verbatim. Never expand a parent issue, sub-issues, or other relationships into additional closers.
Step 2: Gather branch context
Determine the current and default branches:
git branch --show-current
gh repo view --json defaultBranchRef --jq .defaultBranchRef.name
If the current branch is detached or is the default branch, stop and tell the user to create or check out a feature branch.
Read this branch's commits and diff summary:
git log <default-branch>..HEAD --oneline
git diff <default-branch>...HEAD --stat
If both are empty, stop and explain that the branch has no changes relative to the default branch. Suggest checking git status for uncommitted work. For complex changes, read enough modified files to draft an accurate summary.
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.
- 4d ago First seen · 116 lines · 11 tokens per session scan A f6b3816cb2ff
mach12:pr-create is a command published in the GitHub repository LeanAndMean/scramjet (5 stars, last pushed 7d ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,523 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
release
Bump version, update CHANGELOG, build, test, tag, publish.
release-plan
Command "release-plan" from alisunstar/OpenSunstar, covering /rd:release-plan — 发布计划, 先读, 执行, 产物 and 人工确认.
project_init
이 프로젝트를 ocul-pm 추적 대상으로 초기화 (.oculpm/ + 기록 규칙 생성) — 사용자가 직접 실행하는 명시적 시작.
standup
ocul-pm 추적 프로젝트의 오늘 작업 스탠드업 — 일지·플랜 진행을 모아 요약 보고.
inception
새 프로젝트/기능 영역의 설계 시작 — 리서치→사양 확정→3-depth 계획→EVALS→rules 시드.
bump
Version a local plugin from its commits and sync everything downstream.