Borrowing it
Nothing to install: this file belongs to agigante80/actual-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agigante80/actual-mcp-server/main/.claude/commands/merge-pr.mdgit clone --depth 1 https://github.com/agigante80/actual-mcp-serverWrote 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/agigante80/actual-mcp-server/merge-pr)<a href="https://agentmods.dev/commands/agigante80/actual-mcp-server/merge-pr"><img src="https://agentmods.dev/badge/commands/agigante80/actual-mcp-server/merge-pr/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/agigante80/actual-mcp-server/merge-pr"><img src="https://agentmods.dev/badge/commands/agigante80/actual-mcp-server/merge-pr.svg" alt="Reviewed on agentmods" width="80" 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.00210 |
| Opus 5 | $0.00000 | $0.00105 |
| Sonnet 5 | $0.00000 | $0.00042 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
merge-pr 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 11d 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.
What it actually says
Handle a "merge this PR" request the safe, develop-first way: never merge directly; integrate the PR's change onto develop through the full pipeline.
Usage
Accepted argument: <pr-number> (required)
Example: /merge-pr 179
Steps
Follow the merge-pr skill at .claude/skills/merge-pr/SKILL.md. Read that file and execute its pipeline against the PR number passed as the argument.
In short: do NOT run gh pr merge. Inspect the PR, create a gate-ready GitHub ticket to integrate its change onto develop, run that ticket through the implement-ticket pipeline (gate to 10/10, implement by reproducing the PR's change on develop, fast validation, /code-review, mandatory /local-env full, commit + patch bump + push develop, confirm CI green), then close the original PR as superseded. The change reaches main only on the next explicit develop-to-main release. Never touch main. Never use em or en dashes.
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.
- 11d ago First seen · 14 lines · 0 tokens per session scan A 04304655eeab
merge-pr is a command published in the GitHub repository agigante80/actual-mcp-server (54 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 210 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
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.
address-pr-feedback
Systematically address PR review comments. Fetches all threads, categorizes by status (acknowledged, silently fixed, unaddressed), and guides user through posting replies and implementing fixes with explicit approval.
advanced-code-review-context
Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.
create-pr
Create a pull request with proper template discovery and population.
request-review-plan
Request Code Review Phases 1-2: Planning scope and assembling reviewer context.
merge-worktree-resolve
Phase 3: Conflict Resolution - delegate to resolving-merge-conflicts with interface contract context.