await-merge

await-merge is a skill for Claude Code from bengous/claude-code-plugins. It costs 23 tokens per session (322 once invoked), scanned A, original, MIT.

A workflow for waiting for a pull request’s automated checks, choosing a squash or rebase merge, and updating the local base branch. Automated checks are tests or other validations run by the repository.

In plain words
What is it for?
It helps inspect a pull request, watch its checks, merge with linear history, delete the merged branch, and refresh the local base branch.
Why use it?
It prevents merging before checks finish or after a check fails. It also keeps the local base branch current using fast-forward updates.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the git-tools plugin — 6 skills, 2 commands shipped together

Good fit It helps inspect a pull request, watch its checks, merge with linear history, delete the merged branch, and refresh the local base branch.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bengous/claude-code-plugins/await-merge
Install

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.

Any agent
npx skills add bengous/claude-code-plugins --skill await-merge
Clone the repo
git clone --depth 1 https://github.com/bengous/claude-code-plugins

Made for: Claude Code.

Or install git-tools, the plugin that ships this one along with the rest of its 6 skills, 2 commands.

Wrote 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.

agentmods badge for await-merge

README.md
[![agentmods](https://agentmods.dev/badge/skills/bengous/claude-code-plugins/await-merge.svg)](https://agentmods.dev/skills/bengous/claude-code-plugins/await-merge)
Your own site
<a href="https://agentmods.dev/skills/bengous/claude-code-plugins/await-merge"><img src="https://agentmods.dev/badge/skills/bengous/claude-code-plugins/await-merge.svg" alt="Measured on agentmods" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 322 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.00322
Opus 5 $0.00012 $0.00161
Sonnet 5 $0.00005 $0.00064
Haiku 4.5 $0.00002 $0.00032

Measured 4d ago against content hash 918b405e67b5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

await-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 4d 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.

git-tools/skills/await-merge/SKILL.md · 26 lines

What it actually says

Await Merge

  1. Target. $ARGUMENTS, else the PR of the current branch: gh pr view <n> --json number,title,url,baseRefName,commits. None found: stop and ask for the number.

  2. Strategy. One question, with the commit subjects in it:

    • Squash: the commits become one. Default when they are not curated.
    • Rebase: the commits land as they are. Only when each one is atomic.

    Never a merge commit; the history stays linear.

  3. Watch. gh pr checks <n> --watch --fail-fast. A failing check: report its name and stop. No retry, no merge. No checks reported: say so and continue.

  4. Merge. gh pr merge <n> --squash|--rebase --delete-branch. An error: report it verbatim and stop.

  5. Local. git switch <baseRefName> then git pull --ff-only.

  6. Report. The PR URL, the strategy, the new tip of the base branch.

Changes

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.

  1. 4d ago First seen · 26 lines · 23 tokens per session scan A 918b405e67b5

Subscribe to this mod's changes

await-merge is a skill published in the GitHub repository bengous/claude-code-plugins (4 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 322 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.