A command that opens a pull request, a review page for proposed code changes, against the repository’s integration branch.

Use it to verify the working tree and task checklist, run the change review, prepare the English description, and open the pull or merge request.

It gathers the required project settings and checks before opening the request, reducing missed tasks or incorrect branch targets.

pr-open — Command by iolairus

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/iolairus/borderlint/pr-open

Clone the repo

git clone --depth 1 https://github.com/iolairus/borderlint

Made for: Claude Code.

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 489 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.

Model	Per session	Once invoked
Fable 5	$0.00017	$0.00489
Opus 5	$0.00009	$0.00244
Sonnet 5	$0.00003	$0.00098
Haiku 4.5	$0.00002	$0.00049

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

Security

Grade A, and why

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

.claude/commands/pr-open.md · 25 lines

What it actually says

Open a pull/merge request for the change $ARGUMENTS (or the one inferred from the current branch — strip a leading Jira key like PROJ-123- from the branch name before matching against openspec/changes/).

Steps

Read workflow.yaml (git.integration_branch, git.work_mode, platform.provider). Verify: working tree clean, all tasks in tasks.md checked. If tasks remain, list them and ask whether to continue as draft.

If the current branch IS the integration branch (flexible mode), there is nothing to open a PR against: tell the user, and offer either (a) skip the PR and go straight to /ship, or (b) move the unpushed commits to a new feature branch (named feature/<task id>-<change> if the change is linked to a task with a real Jira key, else feature/<change>) via git branch <name> && git reset --hard origin/<integration> to get a reviewed PR.
Run /review-change <change> (spec-reviewer). On REVISE, show findings and stop unless the user overrides.
Write the PR description in English (the repo's only content language).
Build the PR description from templates/pr-description.md, filling it from proposal.md, the delta specs, the branch's commit log, and the linked task (frontmatter change: match in backlog/tasks/).
Detect the platform:
- provider: auto → parse git remote get-url origin; github.com → gh, gitlab → glab. Check the CLI exists (command -v).
- With a CLI: push the branch and create the PR targeting the integration branch, title <type>(<change>): <proposal title>.
- Without CLI or provider: none: push the branch, write the description to backlog/exports/pr/<change>.md, and print the compare URL so the user can open the PR manually.
Update the linked task frontmatter to status: in-progress if not already. Print the PR URL (or export path) and suggest /ship <change> once approved.

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.

2d ago First seen · 25 lines · 17 tokens per session scan A 88f7d0aebd01

Subscribe to this mod's changes

pr-open is a command published in the GitHub repository iolairus/borderlint (7 stars, last pushed 9d ago), licensed MIT. It adds 17 tokens to every session and 489 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.

Code review Git and workflow Planning

pr-open

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

git

checklist

clarify

specify

analyze

constitution