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.
git clone --depth 1 https://github.com/synaptiai/synapti-marketplaceWrote 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/synaptiai/synapti-marketplace/gh-merge)<a href="https://agentmods.dev/commands/synaptiai/synapti-marketplace/gh-merge"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/gh-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/synaptiai/synapti-marketplace/gh-merge"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/gh-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.00000 | $0.01715 |
| Opus 5 | $0.00000 | $0.00857 |
| Sonnet 5 | $0.00000 | $0.00343 |
| Haiku 4.5 | $0.00000 | $0.00171 |
Grade A, and why
gh-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 11d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge PR #$ARGUMENTS
Merge an approved pull request with standardized settings.
Tool Usage: This workflow uses the AskUserQuestion tool to confirm merge options and get explicit approval before executing irreversible actions.
Process
-
Fetch PR details:
gh pr view $ARGUMENTS --json number,title,state,isDraft,headRefName,baseRefName,mergeable,reviewDecision,statusCheckRollup -
Check for unresolved conversations:
# Get review threads with pending status gh api repos/{owner}/{repo}/pulls/$ARGUMENTS/comments --jq '[.[] | select(.in_reply_to_id == null)] | length'If unresolved threads exist, warn user before proceeding.
-
Check for stale approval (commits since last approval):
# Check if PR was updated after last approval gh pr view $ARGUMENTS --json reviews,commits --jq '{last_approval: [.reviews[] | select(.state == "APPROVED")] | last | .submittedAt, last_commit: .commits | last | .committedDate}'If PR was updated since approval, warn: "PR #X has been updated since last approval - may need re-review"
-
Verify prerequisites:
- PR state must be
OPEN - PR must NOT be a draft (
isDraft: false) - PR must be
MERGEABLE - Review decision must be
APPROVED(or no reviews required) - All status checks must pass
- All conversation threads resolved (or acknowledged)
- PR state must be
-
If prerequisites not met: Stop and report what's blocking the merge:
- Draft PR → "PR is a draft. Mark as ready for review first."
- Not approved → "PR requires approval before merging"
- Checks failing → "CI checks are failing: [list failed checks]"
- Merge conflicts → "PR has merge conflicts that need to be resolved"
- Already merged/closed → "PR is already [merged/closed]"
- Unresolved threads → "PR #X has N unresolved conversation threads"
- Stale approval → "PR #X has been updated since last approval - may need re-review"
-
Get merge approval using the AskUserQuestion tool:
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.
- 11d ago First seen · 213 lines · 0 tokens per session scan A 2276dd0d5c00
gh-merge is a command published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,715 tokens. 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 commands, from other repositories
create-worktree
Follow these steps to create a git worktree.
ship
Ship workflow — detect base branch, merge, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR.
document-release
Post-ship documentation update — reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped.
deploy
Start Phase 6 — propose a deployment for human approval and, once approved, execute with post-deploy verification.
resolve-review
Resolve reviewer feedback - from GitHub PRs, chat, or any reviewer.
release
Release the plugin — bump version across 4 files, then optionally commit, tag, push, and create a GitHub Release.