Borrowing it
Nothing to install: this file belongs to kavo-labs/kavo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kavo-labs/kavo/main/.claude/commands/merge.mdgit clone --depth 1 https://github.com/kavo-labs/kavoWrote 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/commands/kavo-labs/kavo/merge)<a href="https://agentmods.dev/commands/kavo-labs/kavo/merge"><img src="https://agentmods.dev/badge/commands/kavo-labs/kavo/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/commands/kavo-labs/kavo/merge"><img src="https://agentmods.dev/badge/commands/kavo-labs/kavo/merge.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.00017 | $0.00899 |
| Opus 5.5 | $0.00007 | $0.00360 |
| Sonnet 5.5 | $0.00003 | $0.00180 |
| Haiku 4.5 | $0.00002 | $0.00090 |
Grade A, and why
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 1mo 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Branch: !
git rev-parse --abbrev-ref HEAD - Working tree: !
git status --short - PR: !
gh pr view $ARGUMENTS --json number,title,state,isDraft,mergeable,mergeStateStatus,reviewDecision,url 2>/dev/null || echo "NO PR" - Checks: !
gh pr checks $ARGUMENTS 2>/dev/null || echo "no checks reported"
Your task
Close the loop on this PR. Argument: $ARGUMENTS
-
Refuse to merge if any of these hold. Report which one and stop:
- there is no matching PR;
- the PR is still a draft;
- any required check is failing or still running — wait for it, do not merge past it;
mergeableis false, or there are conflicts withmain;
If the only problem is that checks are still running, say so and offer to wait rather than merging blind.
-
Say what you are about to merge — PR number, title, commit count, and the issue it closes — and get the user's go-ahead before the merge itself. This is the irreversible step.
-
Merge with squash, keeping history linear and one commit per issue. Always pass an authored
--subjectand--body— never letghfall back to its default squash body, which is the concatenated list of branch commit messages (* feat(scope): …bullets and all). release-please parses the whole merged message, and a body full of pseudo-headers and nestedcall(inner())code spans has silently defeated its parser before (fix commit could not be parsed→ the commit is dropped from the changelog and triggers no bump; commit 9fa1434 / #354).gh pr merge <n> --squash --delete-branch \ --subject "feat(core): …" \ --body "$(cat <<'EOF' One or two plain-prose paragraphs summarizing the change. Refs #<n> EOF )"Write the subject as a Conventional Commit matching this repo's style (
feat(core): …). Keep the body plain prose: no* type(scope):bullet lines, and rephrase anyouter(inner())nesting (metadataForofrelation.target(), notmetadataFor(relation.target())).
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.
- 1mo ago First seen · 85 lines · 17 tokens per session scan A a5956fc00e4e
merge is a command published in the GitHub repository kavo-labs/kavo (17 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 899 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-02.
Other commands, from other repositories
speckit.companion.living-sync
Sync living specs from your current changes — group working-tree changes (uncommitted included) by capability and update every affected spec in one pass (opt-in, update-not-regenerate, never halts).
push-changes
If no topic provided, just document the recent changes. If a topic is provided, focus on documenting that topic.
sync-tutorials
Commit and push your tutorials to the GitHub repository for backup and mobile reading.
git-commit
Based on the above changes, create a single git commit. Use the Angular commit message format:.
commit-push-pr
Commit, push, and open a PR (includes changeset creation).
commit
Based on the above changes, create a single git commit.