apple-mail-mcp: Command for Claude Code

.claude/commands/merge-and-status.md

merge-and-status is a command for Claude Code from TG-Techie/apple-mail-mcp. It costs 0 tokens per session (903 once invoked), scanned A, a copy of merge-and-status, MIT.

A command for completing the current GitHub pull request, updating the local main branch, and reporting outstanding project work. A pull request is a proposed code change awaiting review or merging.

In plain words
What is it for?
It is for maintainers who want to wait for checks, squash-merge the current pull request, delete its branch, pull main, and review other contributors’ open pull requests and issues.
Why use it?
It gathers several release and maintenance checks into one routine, reducing the chance of forgetting open contributions, issues, or milestone work.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is TG-Techie/apple-mail-mcp's own configuration. It tells Claude Code how to work on apple-mail-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything apple-mail-mcp configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/TG-Techie/apple-mail-mcp/main/.claude/commands/merge-and-status.md
Clone the repo
git clone --depth 1 https://github.com/TG-Techie/apple-mail-mcp

Made for: Claude Code.

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 merge-and-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/tg-techie/apple-mail-mcp/merge-and-status/github.svg)](https://agentmods.dev/commands/tg-techie/apple-mail-mcp/merge-and-status)
Your own site
<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.

agentmods 80×15 button for merge-and-status

Your own site · 80×15
<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>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 903 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 86% copy Near-identical to another mod 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.00000 $0.00903
Opus 5 $0.00000 $0.00451
Sonnet 5 $0.00000 $0.00181
Haiku 4.5 $0.00000 $0.00090

Measured 10d ago against content hash 5b507813df58, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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.

Origin

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.

.claude/commands/merge-and-status.md · 65 lines

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

  1. Find the open PR for the current branch:

    gh pr list --head "$(git branch --show-current)" --state open --json number --jq '.[0].number'
    
  2. Wait for CI checks to pass:

    gh pr checks <number> --watch
    
  3. Squash merge the PR and delete the branch:

    gh pr merge <number> --squash --delete-branch
    
  4. Switch to main and pull:

    git checkout main && git pull
    
  5. 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.
  6. 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.
  7. 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'
    
  8. List open issues on that milestone:

    gh issue list --milestone "<milestone>" --state open
    
  9. 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)
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. 10d ago First seen · 65 lines · 0 tokens per session scan A 5b507813df58

Subscribe to this mod's changes

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.