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.
git clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packWrote 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/evan043/claude-cli-advanced-starter-pack/pr-merge.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/pr-merge.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/pr-merge.template.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.00000 | $0.07164 |
| Opus 5 | $0.00000 | $0.03582 |
| Sonnet 5 | $0.00000 | $0.01433 |
| Haiku 4.5 | $0.00000 | $0.00716 |
Grade A, and why
pr-merge.template 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 8d 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 — 995 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Runtime Compatibility
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:
AskUserQuestion=> ask the user directly in chat.WebSearch/WebFetch=> use available web tools (search_query,open,find) and cite links.Read/Write=> use shell/filesystem tools in this workspace.- Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
- Keep intent and output format identical; only adapt execution mechanics.
description: Merge PR with interactive blocker resolution, safety checkpoints, and contributor messaging allowed-tools:
- Bash
- Read
- AskUserQuestion
/pr-merge - Interactive PR Merge
An intelligent merge assistant that handles all PR scenarios safely, with clear communication to contributors.
{{#if versionControl.owner}}
Usage
/pr-merge # Show menu of all open PRs
/pr-merge 42 # Merge PR #42 directly
/pr-merge 42 --worktree # Test PR #42 in isolated worktree first
/pr-merge --dry-run # Preview only, no changes
Worktree Test Mode
Use --worktree or select [W] during merge to:
- Run security scan on PR changes
- Create isolated worktree for testing
- Resolve conflicts safely before merging
- Test features without affecting your main repo
PHASE 0: OPEN PR MENU (Default when no args)
When /pr-merge is called without arguments or a PR number, show an interactive menu of all open PRs.
Step 0.1: Fetch all open PRs with details
gh pr list --repo {{versionControl.owner}}/{{versionControl.repo}} --state open --json number,title,body,createdAt,author,isDraft,mergeable,mergeStateStatus,reviewDecision,statusCheckRollup,additions,deletions,changedFiles --limit 20
Step 0.2: Display the PR selection menu
Format each PR as a stacked card (mobile-friendly, no word wrapping):
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.
- 8d ago First seen · 995 lines · 0 tokens per session scan A 27918d5c645f
pr-merge.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 7,164 tokens. 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
commit-push-pr
An automated Git workflow that checks a project, synchronizes documentation, commits changes, and can create or merge a GitHub pull request. A pull request is a request for teammates to review and add changes to a shared codebase.
auto
An automated coding workflow runs a software task from planning through code changes, checks, and a pull request. A pull request is a proposed change for review before it is merged into the main codebase.
sync
A command that pulls the latest code from the main Git branch and updates the project's key planning and instruction documents to match it.
pull
A quick command that downloads the latest commits from the main Git branch into the current project.
worktree-cleanup
A command for removing a Git worktree, which is a separate working folder linked to the same repository, after its pull request is merged.
quick-commit
A quick Git command for committing and pushing a small code change. Git is the tool that records code versions and sends them to a shared repository.