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 skills/dryvist/claude-code-plugins/merge-prnpx skills add dryvist/claude-code-plugins --skill merge-prgit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWrote 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/skills/dryvist/claude-code-plugins/merge-pr)<a href="https://agentmods.dev/skills/dryvist/claude-code-plugins/merge-pr"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/merge-pr.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 | $0.00071 | $0.02152 |
| Opus 5 | $0.00036 | $0.01076 |
| Sonnet 5 | $0.00014 | $0.00430 |
| Haiku 4.5 | $0.00007 | $0.00215 |
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 3d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge PR
Validates readiness, invokes /finalize-pr for soft blocks, then merges.
Hard stops abort immediately. Some cases require human action: closed/merged PR,
draft, unresolvable conflicts, unrecoverable CI, or more than 100 review threads.
State warning: Branch state, remote tracking, and PR status change between invocations. Re-run all git/gh commands from Step 1.
Critical Rules
- Run the GraphQL readiness gate on every invocation before merging
- PR metadata updates are
/finalize-pr's responsibility - Invoke
/finalize-prfor soft blocks; abort on hard stops with reason - Merge commit is the default;
--squash/-sopts into a squash merge - Squash and rebase are never used to merge into
mainon a git-flow repo — Step 0 guards this. Plain merge commit intomainon a git-flow repo IS allowed — that's the/promote-releasepath.
Step 0: Refuse Squash/Rebase Into Main On Git-Flow Repos
Resolve the PR's base branch and the repo's default branch:
BASE_BRANCH=$(gh pr view <PR_NUMBER> --json baseRefName --jq '.baseRefName')
DEFAULT_BRANCH=$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name')
If BASE_BRANCH == main AND DEFAULT_BRANCH == develop (repo is on git-flow —
see /gh-cli-patterns Canonical Default-Branch Detection):
-
--squash/-swas passed → abort immediately, no finalize:"This is a
develop→mainpromotion PR on a git-flow repo.mainaccepts merge commits only — squash and rebase are banned by ruleset, no exceptions. Run/promote-releaseinstead, or merge manually withgh pr merge --merge." -
No
--squash(default merge commit) → this is a legitimate promotion. Continue to Step 1, but note in the final report that/promote-releaseis the normal entry point for this (it also opens the PR and explains release-please) — this invocation may be a manual equivalent of that.
Otherwise (trunk repo, or a git-flow repo's ordinary feature PR into develop),
continue to Step 1 with the requested (or default) merge method.
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.
- 3d ago First seen · 211 lines · 71 tokens per session scan A 1f2c47d837ac
merge-pr is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 71 tokens to every session and 2,152 once invoked, about $0.0004 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.
Other skills, from other repositories
rspec
This skill should be used when the user asks to "write specs", "create spec", "add RSpec tests", "fix failing spec", or mentions RSpec, describe blocks, it blocks, expect syntax, test doubles, or matchers. Should also be used when editing spec.rb files, working in spec/ directory, planning implementation phases that…
activerecord
This skill should be used when the user asks to "write a migration", "add a column", "add column to table", "create an index", "add a foreign key", "set up associations", "fix N+1 queries", "optimize queries", "add validations", "create callbacks", "use eager loading", or mentions ActiveRecord, belongsto, hasmany…
dragonruby
This skill should be used when the user asks to "create a game", "make a game", "game development", "dragonruby", "drgtk", "game loop", "tick method", "sprite rendering", "game state", or mentions args.outputs, args.state, args.inputs, coordinate system, collision detection, animation frames, or scene management.…
draper-decorators
This skill should be used when the user asks to "create a decorator", "write a decorator", "move logic into decorator", "clean logic out of the view", "isn't it decorator logic", "test a decorator", or mentions Draper, keeping views clean, or representation logic in decorators. Should also be used when editing…
mcp-server
This skill should be used when the user asks to "create an MCP server", "build MCP tools", "define MCP prompts", "register MCP resources", "implement Model Context Protocol", or mentions the mcp gem, MCP::Server, MCP::Tool, JSON-RPC transport, stdio transport, or streamable HTTP transport. Should also be used when…
ratatui-ruby
This skill should be used when the user asks to "create a TUI", "terminal interface", "terminal UI", "ratatui", "ratatui-ruby", "inline viewport", "full-screen terminal app", "terminal widgets", "tui.draw", "tui.pollevent", or mentions RatatuiRuby.run, managed loop, terminal rendering, Tea MVU, or building CLI…