pr-create

A pull-request creation workflow for the current Git branch. A pull request is a request for teammates to review and merge code, usually with a summary, testing notes, and a linked issue.

In plain words
What is it for?
Use it to create a pull request, link an issue, summarize changes, describe the test plan, and include relevant context.
Why use it?
It structures the pull request and gathers context from the branch and commits, reducing manual preparation.

Command

Install

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.

agentmods
npx agentmods add commands/leanandmean/mach10/pr-create
Clone the repo
git clone --depth 1 https://github.com/LeanAndMean/mach10
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,217 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00011 $0.02217
Opus 5 $0.00005 $0.01108
Sonnet 5 $0.00002 $0.00443
Haiku 4.5 $0.00001 $0.00222

Measured 2d ago against content hash 33d95d33c414, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 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.

commands/pr-create.md · 194 lines

How it starts

The opening of the file, as written. The whole thing — 194 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 issue linkage.

Context (optional): $ARGUMENTS

Step 0: Parse input and create task list

The user may provide:

  • An issue number to link (e.g., 55)
  • An issue number plus additional context (e.g., 55 focus on the API changes)
  • Nothing — you will infer context from the branch and commits

Extract the issue number if provided. Note any additional context for use when drafting the PR body. If the input is ambiguous (e.g., it's unclear whether a token is an issue number or context), use free-text to ask the user to clarify.

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 4 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: Gather context Gathering context
Step 2 Step 2: Draft PR and get approval Drafting PR
Step 3 Step 3: Create pull request Creating pull request
Step 4 Step 4: Confirm PR and suggest next steps Confirming PR

Mark Step 0 complete.

Step 1: Gather context

Mark Step 1 in progress.

Determine the current branch:

git branch --show-current

If the output is empty (detached HEAD state), stop and tell the user to create or checkout a branch first. Leave Step 1 as in_progress.

Determine the default branch of the repository:

gh repo view --json defaultBranchRef --jq .defaultBranchRef.name

If the current branch is the default branch, stop and tell the user to create a feature branch first. Leave Step 1 as in_progress.

Read the full file on GitHub · 194 lines

Changes

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.

  1. 2d ago First seen · 194 lines · 0 tokens per session scan A 33d95d33c414

Subscribe to this mod's changes

pr-create is a command published in the GitHub repository LeanAndMean/mach10 (20 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 2,217 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.