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-issue-plangit 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-plan)<a href="https://agentmods.dev/commands/leanandmean/scramjet/mach12-issue-plan"><img src="https://agentmods.dev/badge/commands/leanandmean/scramjet/mach12-issue-plan.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.05481 |
| Opus 5 | $0.00009 | $0.02740 |
| Sonnet 5 | $0.00003 | $0.01096 |
| Haiku 4.5 | $0.00002 | $0.00548 |
Grade A, and why
mach12:issue-plan 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 today.
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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Plan
Goals
- Produce one durable, standalone implementation plan grounded in the complete issue history, current codebase, project guidance, and explicit user decisions.
- Select a minimum-sufficient architecture and proportionate test strategy, divided into dependency-aware stages that each fit one implementation session.
- Publish the verified plan, create its feature branch, and report assignment outcomes before offering next-step routing.
Guardrails
This command is strictly for planning. Do NOT:
- Implement any code changes -- no file edits, no file writes
- Attempt to execute the plan within this session
Implementation happens in separate sessions via /mach12:issue-implement.
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 planning.
Step 2: Read the issue
Delegate to:
/mach12:gh-issue-read <issue-number>
The subroutine returns the issue title, body, parent createdAt and updatedAt, and the full comments stream with comment creation timestamps. Parse and understand:
- The problem statement
- Any constraints or requirements mentioned
- Prior discussion or decisions in the comments
- Acceptance criteria (if specified)
Step 3: Read contribution guidelines
Before exploring the code, 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 (e.g., models, migrations, API routes, services, UI, documentation), testing expectations (test frameworks, coverage requirements, test types), documented development tools, and any other requirements that should inform the implementation plan.
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.
- today Changed · +16 lines af1651d55ccf
- 5d ago First seen · 290 lines · 17 tokens per session scan A 4d63dedeffbd
mach12:issue-plan is a command published in the GitHub repository LeanAndMean/scramjet (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 5,481 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
project_init
이 프로젝트를 ocul-pm 추적 대상으로 초기화 (.oculpm/ + 기록 규칙 생성) — 사용자가 직접 실행하는 명시적 시작.
inception
새 프로젝트/기능 영역의 설계 시작 — 리서치→사양 확정→3-depth 계획→EVALS→rules 시드.
standup
ocul-pm 추적 프로젝트의 오늘 작업 스탠드업 — 일지·플랜 진행을 모아 요약 보고.
rebuildrestart
Command "rebuildrestart" from rwliebs/Dossier, covering rebuildrestart, rebuild and restart the dossier dev server, usage and ./scripts/rebuild-and-restart.sh # dev server (default).
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.