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/mach10/issue-plangit clone --depth 1 https://github.com/LeanAndMean/mach10What 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.00017 | $0.03466 |
| Opus 5 | $0.00009 | $0.01733 |
| Sonnet 5 | $0.00003 | $0.00693 |
| Haiku 4.5 | $0.00002 | $0.00347 |
Grade A, and why
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 2d 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Plan
You are creating a staged implementation plan for a GitHub issue. Your goal is to deeply understand the issue, explore the relevant codebase, and produce a plan where each stage can be implemented within a single Claude Code CLI session.
User input: $ARGUMENTS
Note: This command performs best with an Opus-class model. On Sonnet or Haiku, results may be shallower.
Guardrails
This command is strictly for planning. Do NOT:
- Use
EnterPlanModeor enter plan mode - Implement any code changes -- no file edits, no file writes
- Attempt to execute the plan within this session
Implementation happens in separate sessions via /mach10:issue-implement.
Step 0: Parse input and create task list
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.
After parsing input, create the progress-tracking task list. Create a task for Step 0 and immediately mark it in progress. Then create tasks for each of the remaining 6 steps one at a time, in step order, all starting as pending. Task list display order matches creation order, so each task must be a separate sequential call -- do not batch multiple task creations in a single message. Store each returned task ID for later use -- do not assume IDs are sequential.
| Task | Subject | activeForm |
|---|---|---|
| Step 0 | Step 0: Parse input and create task list | Parsing input |
| Step 1 | Step 1: Read the issue | Reading the issue |
| Step 2 | Step 2: Explore the codebase | Exploring the codebase |
| Step 3 | Step 3: Ask clarifying questions | Asking clarifying questions |
| Step 4 | Step 4: Design architecture | Designing architecture |
| Step 5 | Step 5: Draft the plan | Drafting the plan |
| Step 6 | Step 6: Post plan and create branch | Posting plan and creating branch |
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.
- 2d ago First seen · 257 lines · 17 tokens per session scan A 2939dc5986a8
issue-plan is a command published in the GitHub repository LeanAndMean/mach10 (20 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 3,466 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-30.
Other commands, from other repositories
loop
Iteratively fix issues until all resolved or max iterations reached.
OpenSpec: Apply
Implement an approved OpenSpec change and keep tasks in sync.
retex
Retex - Capture lesson learned dans memory après fix, rollback, erreur.
task-integrate
PitWay: Apply a dispatched task's worktree commit to the main tree.
pantoum-studio
Launch the PANTOUM Studio webapp for visual configuration and upgrade monitoring.
scenarios
The table of Gherkin scenarios the integration tests cover — so "what is actually tested?" is a question you can answer without running anything.