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 skills add tomzx/agents --skill merge-prgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/merge-pr)<a href="https://agentmods.dev/skills/tomzx/agents/merge-pr"><img src="https://agentmods.dev/badge/skills/tomzx/agents/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/skills/tomzx/agents/merge-pr"><img src="https://agentmods.dev/badge/skills/tomzx/agents/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.00024 | $0.00905 |
| Opus 5.5 | $0.00010 | $0.00362 |
| Sonnet 5.5 | $0.00005 | $0.00181 |
| Haiku 4.5 | $0.00002 | $0.00090 |
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 22d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge PR
Verifies that a pull request has the required approvals and passing CI checks, then merges it and cleans up the branch.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - If no argument is provided, target the pull request from
$PR_NUMBER(and$REPO). ghCLI authenticated with write access to the target repository- PR number (
$1) identifying an open pull request - All review feedback addressed (run
/handle-pr-reviewer-feedbackfirst if comments are unresolved)
Workflow
Fetch PR status ($1)
|
v
All approvals obtained?
/ \
Yes No
| |
v v
CI checks Report missing
passing? approvals, stop
/ \
Yes No
| |
v v
Merge /handle-pr-ci
PR (fix, then re-check)
|
v
Delete remote branch
|
v
Delete prs/<n>/review tag
|
v
Confirm issue closed
Steps
-
Fetch the current PR status:
gh pr view $1 --json state,reviews,statusCheckRollup,mergeStateStatus,headRefName,closingIssuesReferences -
Check approvals: confirm at least one reviewer has approved and no reviewers have requested changes. If approvals are missing or changes are requested, report the status and stop.
-
Check CI: confirm all required status checks are passing. If any are failing or pending, invoke
/handle-pr-ci $1to diagnose and fix before continuing. -
Present the merge summary to the user (PR title, approvals, checks) and ask for confirmation.
-
On confirmation, merge the PR:
gh pr merge $1 --squash --delete-branchUse
--squashby default for a clean history. If the project uses merge commits or rebase, adjust accordingly. -
Confirm the remote branch was deleted. If not, delete it:
gh api repos/{owner}/{repo}/git/refs/heads/{branch} -X DELETE -
Delete the review checkpoint tag left by validate-pr / verify-pr / review-pr (see
sdlc/references/shared.md, Review checkpoint tags):git tag -d "prs/$1/review" 2>/dev/null || true
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.
- 22d ago Changed · +10 lines 8d6588b82cae
- 28d ago Changed · +9 lines 0c7c5b02d0c7
- 1mo ago First seen · 104 lines · 24 tokens per session scan A aa385414fc13
merge-pr is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 905 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
otto-drive-pr
PR mergeability, CI, and live preview.
voicestudio-maintainer
Triage GitHub issues, review contributor pull requests, diagnose CI, and prepare explicitly requested releases for VoiceStudio's Electron desktop app and Python backend. Use for repository maintenance work, not ordinary VoiceStudio audio generation.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…