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-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-issue-create)<a href="https://agentmods.dev/commands/leanandmean/scramjet/mach12-issue-create"><img src="https://agentmods.dev/badge/commands/leanandmean/scramjet/mach12-issue-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.03768 |
| Opus 5 | $0.00005 | $0.01884 |
| Sonnet 5 | $0.00002 | $0.00754 |
| Haiku 4.5 | $0.00001 | $0.00377 |
Grade C, and why
mach12:issue-create scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
trap 'rm -rf "$duplicate_search_dir"' EXIT How it starts
The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Issue
You are identifying and accurately capturing the problem that motivated this command, then creating a structured GitHub issue after explicit user approval.
Step 1: Identify the problem
Use evidence in this order:
- descriptive content supplied with the command.
- A structured artifact explicitly supplied or adopted by the user.
- The immediate session context and recent conversation that led to this invocation, including an encountered bug, requested capability, deferred finding, confusing workflow, or unresolved concern.
- Relevant recent repository observations already established in the active session.
Preserve user intent, experienced symptoms, constraints and non-goals, clarification answers, and other session-only problem evidence as attributed evidence, including when that evidence also contains objectively checkable factual premises. Preserve the attribution while separately verifying only any checkable premise whose falsity would materially change the problem identity, actual behavior, impact, proposed outcome, or acceptance criteria. Treat implementation preferences as preferences or explicit constraints, not as contradictions that must be resolved during issue creation.
Do not search historical sessions merely because the command has no descriptive argument. Use the general prior-session fallback only when current evidence points to relevant earlier work and the missing detail matters.
Classify the evidence as one clear candidate problem, multiple distinct candidate problems, or no supported candidate:
- If one candidate is clear, proceed without asking the user to repeat evident context.
- If one candidate is plausible but uncertain, state what likely prompted the command and ask for confirmation or correction.
- If multiple distinct candidates are supported, ask which one should become the issue and do not silently combine unrelated problems. A tracking issue or multiple issues requires explicit user direction.
- If no supported candidate is clear, ask what problem, missing capability, or concern the user wants captured.
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 · 242 lines · 11 tokens per session scan C 2dae2a737728
mach12:issue-create is a command published in the GitHub repository LeanAndMean/scramjet (5 stars, last pushed 6d ago), licensed Apache-2.0. It adds 11 tokens to every session and 3,768 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
factory-report
Linear status report across configured repos — queue depth, triage backlog, ready-to-dispatch, blocked/held.
app-status
Show the current state of the project — vision, sprint goal, board, blockers, daily report.
project_init
이 프로젝트를 ocul-pm 추적 대상으로 초기화 (.oculpm/ + 기록 규칙 생성) — 사용자가 직접 실행하는 명시적 시작.
resume-loop
You are resuming a l00prite-managed project. Treat .l00prite/ as the shared source of truth across Claude, Codex, GPT, Gemini, and future agents.
handoff-summary
Prepare a cross-agent handoff for a l00prite-managed project.
bob-new
Provision a well-formed task onto the Bob board from a rough description.