Borrowing it
Nothing to install: this file belongs to TG-Techie/apple-mail-mcp. 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/TG-Techie/apple-mail-mcp/main/.claude/commands/merge-and-status.mdgit clone --depth 1 https://github.com/TG-Techie/apple-mail-mcpWrote 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/tg-techie/apple-mail-mcp/merge-and-status)<a href="https://agentmods.dev/commands/tg-techie/apple-mail-mcp/merge-and-status"><img src="https://agentmods.dev/badge/commands/tg-techie/apple-mail-mcp/merge-and-status/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/tg-techie/apple-mail-mcp/merge-and-status"><img src="https://agentmods.dev/badge/commands/tg-techie/apple-mail-mcp/merge-and-status.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.00903 |
| Opus 5 | $0.00000 | $0.00451 |
| Sonnet 5 | $0.00000 | $0.00181 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
merge-and-status 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 10d 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.
This is a copy
86% identical to merge-and-status — 67 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Merge the current PR, pull main, surface any open contributor PRs and untriaged contributor issues, and show open milestone issues.
Steps
-
Find the open PR for the current branch:
gh pr list --head "$(git branch --show-current)" --state open --json number --jq '.[0].number' -
Wait for CI checks to pass:
gh pr checks <number> --watch -
Squash merge the PR and delete the branch:
gh pr merge <number> --squash --delete-branch -
Switch to main and pull:
git checkout main && git pull -
Surface open contributor PRs (any PR the current GitHub user did not author). This is the catch-net for external contributions that might otherwise sit unreviewed for weeks:
GIT_USER=$(gh api user --jq .login) gh pr list --state open --json number,title,author,createdAt \ --jq "map(select(.author.login != \"$GIT_USER\")) | .[] | \"#\(.number)|\(.author.login)|\(.title)|\(.createdAt[:10])\""Behavioral rules for displaying the result:
- Render as a table with columns: PR #, author, title, opened-on date.
- If any rows appear, call them out at the top of the final response — e.g., "⚠️ N contributor PR(s) need attention." Don't bury this below the milestone-issues list.
- If the same author appears multiple times, group them together in the table.
- Dependabot PRs count as contributor PRs for visibility purposes (they need rebase nudges or merges too).
- If zero rows, say "No open contributor PRs" so the user gets positive confirmation rather than ambiguity.
-
Surface untriaged contributor issues (open issues filed by anyone other than the current GitHub user that are NOT assigned to a milestone). The reasoning for the no-milestone filter: assigned issues have already been triaged and are visible elsewhere — the truly invisible ones are the unassigned ones.
GIT_USER=$(gh api user --jq .login) gh issue list --state open --limit 50 --json number,title,author,createdAt,milestone \ --jq "map(select(.author.login != \"$GIT_USER\")) | map(select(.milestone == null)) | .[] | \"#\(.number)|\(.author.login)|\(.title)|\(.createdAt[:10])\""Behavioral rules (mirror the contributor-PR step):
- Render as a table with columns: issue #, author, title, opened-on date.
- If any rows appear, call them out at the top of the final response alongside (or below) the contributor-PR call-out — e.g., "⚠️ N untriaged contributor issue(s) need attention."
- If the same author appears multiple times, group them together in the table.
- If zero rows, say "No untriaged contributor issues" for positive confirmation.
-
Determine the current milestone. Look at the most recent closed PR's milestone, or find the earliest open milestone:
gh api repos/:owner/:repo/milestones --jq 'sort_by(.due_on // .title) | map(select(.state == "open")) | .[0].title' -
List open issues on that milestone:
gh issue list --milestone "<milestone>" --state open -
Display results in this order:
- Merge confirmation (which PR landed, what was authored by whom)
- Contributor-PR section from step 5 — call-out if any exist, or "No open contributor PRs"
- Untriaged contributor issues section from step 6 — call-out if any exist, or "No untriaged contributor issues"
- Current milestone + its open issues as a formatted table (issue #, title, labels)
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.
- 10d ago First seen · 65 lines · 0 tokens per session scan A 5b507813df58
merge-and-status is a command published in the GitHub repository TG-Techie/apple-mail-mcp (0 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 903 tokens. A static security scan graded it A with 0 findings. It is 86% identical to merge-and-status, differing in 67 lines, and is treated as a copy.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
weekly-summary
Generate weekly work summary from git activity.
next
Suggest the most likely next workflow action based on current context.