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 bengous/claude-code-plugins --skill await-mergegit clone --depth 1 https://github.com/bengous/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/bengous/claude-code-plugins/await-merge)<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>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.00023 | $0.00322 |
| Opus 5 | $0.00012 | $0.00161 |
| Sonnet 5 | $0.00005 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
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.
What it actually says
Await Merge
-
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. -
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.
-
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. -
Merge.
gh pr merge <n> --squash|--rebase --delete-branch. An error: report it verbatim and stop. -
Local.
git switch <baseRefName>thengit pull --ff-only. -
Report. The PR URL, the strategy, the new tip of the base branch.
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.
- 4d ago First seen · 26 lines · 23 tokens per session scan A 918b405e67b5
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.
Other skills, from other repositories
release
Verify, sweep docs, cut a version — then hand the release sequence back.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
repo-harness-check
Verification entrypoint for repo-harness workflow readiness. Runs workflow gates, task sync, contract checks, inspector, and migration dry-run before merge or release.
graincrawl
Maintain, verify, and release graincrawl, the local-first Granola archive CLI, including SQLite archive behavior, read-only Granola source boundaries, Homebrew tap packaging, and crawlkit-powered TUI/snapshot surfaces.
crawlkit
Maintain and release the crawlkit Go library, preserving downstream compatibility for gitcrawl, slacrawl, discrawl, and notcrawl.
release
Prepare code for release (version bumps, changelog, README updates) and create an annotated tag to trigger the GoReleaser workflow.