Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/flurdy/agent-skillsnpx agentmods add skills/flurdy/agent-skills/ready-to-mergeWrote 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/flurdy/agent-skills/ready-to-merge)<a href="https://agentmods.dev/skills/flurdy/agent-skills/ready-to-merge"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/ready-to-merge/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/flurdy/agent-skills/ready-to-merge"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/ready-to-merge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 6 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium Excessive Agency · line 73 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00059 | $0.04145 |
| Opus 5 | $0.00030 | $0.02073 |
| Sonnet 5 | $0.00012 | $0.00829 |
| Haiku 4.5 | $0.00006 | $0.00415 |
Grade A, and why
ready-to-merge 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ready to Merge — Pre-Merge Gate
Verify a PR is safe to merge, present a terse readout, and — only after explicit user approval — squash-merge it.
This skill is a synthesis layer: it calls into /pr-status's scripts, optionally /contract-check, and reuses /review-pr's view/diff scripts. It does NOT reimplement those skills.
Relationship to other skills
/pr-status— passive multi-PR dashboard. This skill is single-PR, decision-oriented, and ends with an action./review-pr— deep AC-vs-diff review. Linked but not auto-invoked. Suggest it if the diff is large or AC fit is unclear./contract-check— read-only contract health audit. Auto-invoked only when pacts are present in the repo, and scoped tostatus(summary only)./contract-test— contract test runner (generate → sync → verify). Never auto-invoked here — CI already ran the tests on push. Surfaced as a remediation pointer when/contract-checkflags stale or uncommitted pacts.tracking-auditor(agent) — branch-vs-ticket scope check. Suggest it if the diff looks broader than the ticket.
Usage
/ready-to-merge # PR for current branch
/ready-to-merge 5753 # explicit PR number
/ready-to-merge --no-merge # report only, never offer to merge
Procedure
Phase 1 — Resolve PR
# If no number given:
~/.agents/skills/review-pr/scripts/gh-pr-current-number.sh
# Fallback: gh pr view --json number --jq '.number'
Resolve owner/repo from git remote get-url origin.
Phase 2 — Gather (run in parallel where possible)
Run these in parallel — they're independent fetches:
- PR details (state, mergeState, reviewDecision, checksState, approvers, threads, isDraft, base, head):
~/.agents/skills/pr-status/scripts/gh-pr-details.sh {owner} {repo} {pr} - PR view (title, body, additions, deletions, changedFiles, files):
~/.agents/skills/review-pr/scripts/gh-pr-view.sh {pr} - Diff:
~/.agents/skills/review-pr/scripts/gh-pr-diff.sh {pr} - Stacked children — PRs that target THIS PR's head branch:
gh pr list --base {head-branch} --state open --json number,title,headRefName,url - Local working copy — if the resolved PR matches the current branch, also:
Uncommitted/unpushed work is a hard blocker. Use the wrapper for the unpushed-commits check — never inlinegit status --porcelain ~/.agents/skills/ready-to-merge/scripts/git-unpushed.sh # unpushed commitsgit log @{u}..HEAD. The sandbox flags the bare@{u}..HEADas brace expansion, so it can never be auto-approved.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed 8b496175eb51
- 11d ago First seen · 295 lines · 59 tokens per session scan A 12e04b8fa665
ready-to-merge is a skill published in the GitHub repository flurdy/agent-skills (9 stars, last pushed 4d ago), licensed MIT. It adds 59 tokens to every session and 4,145 once invoked, about $0.0003 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
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
oss-maintainer
Run an open-source project's issue/PR/release loop like a careful human maintainer — triage to root cause, absorb community PRs before duplicating them, gate every merge, ship honest releases, and thank the people doing your QA for free.