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.00796 |
| Opus 5 | $0.00012 | $0.00398 |
| Sonnet 5 | $0.00005 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00080 |
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 5d 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 — 104 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
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 -
Confirm the linked issue was closed automatically (via
Closes #Nin the PR description). If not, close it manually:gh issue close <issue-number>
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.
- 5d ago First seen · 104 lines · 24 tokens per session scan A aa385414fc13
merge-pr is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 796 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-09-03.
Other skills, from other repositories
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
github
Full GitHub CLI control — issues, PRs, code reviews, repo management. Uses gh CLI with auth detection, rate limiting, and templates. Triggers on: github, issue, pull request, PR, code review, repo, branch, label, assignee, milestone, release, workflow, actions.
release
Release gentle-pi through GitHub and npm. Trigger: release, publish, npm publish, GitHub release, version bump.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…
parallel-pr-review
Use when asked to "review the open PRs", review a batch or stack of pull requests, or run a recurring PR-review pass on a repo — especially with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.
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"…