Borrowing it
Nothing to install: this file belongs to LeChabrax/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/LeChabrax/apple-mail-mcp/main/.claude/commands/merge-and-status.mdgit clone --depth 1 https://github.com/LeChabrax/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/lechabrax/apple-mail-mcp/merge-and-status)<a href="https://agentmods.dev/commands/lechabrax/apple-mail-mcp/merge-and-status"><img src="https://agentmods.dev/badge/commands/lechabrax/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/lechabrax/apple-mail-mcp/merge-and-status"><img src="https://agentmods.dev/badge/commands/lechabrax/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.01562 |
| Opus 5 | $0.00000 | $0.00781 |
| Sonnet 5 | $0.00000 | $0.00312 |
| Haiku 4.5 | $0.00000 | $0.00156 |
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
100% identical to merge-and-status — 91 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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. The block below is hardened against a transient empty response that once hid PR #246 across four runs (#253): it echoes the filter identity, retries once on an empty fetch, reports total-vs-filtered counts, and filters via
jq --arg(so an empty identity over-surfaces rather than silently dropping everything):GIT_USER=$(gh api user --jq .login) [ -z "$GIT_USER" ] && echo "WARNING: gh api user returned empty — contributor filter unreliable." echo "Identity for filter: ${GIT_USER:-<empty>}" prs=$(gh pr list --state open --json number,title,author,createdAt) if [ "$(printf '%s' "$prs" | jq 'length')" -eq 0 ]; then # retry a transient empty (#253) sleep 1; prs=$(gh pr list --state open --json number,title,author,createdAt) fi total=$(printf '%s' "$prs" | jq 'length') contrib=$(printf '%s' "$prs" | jq --arg me "$GIT_USER" 'map(select(.author.login != $me))') echo "Open PRs: $total total, $(printf '%s' "$contrib" | jq 'length') by contributors" printf '%s' "$contrib" | jq -r '.[] | "#\(.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.
- Report the count line. A
total> 0 with0contributor PRs is only expected when every open PR is the maintainer's; otherwise treat it as a possible dropped-filter miss and re-run before reporting "none." (#253)
-
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) [ -z "$GIT_USER" ] && echo "WARNING: gh api user returned empty — contributor filter unreliable." echo "Identity for filter: ${GIT_USER:-<empty>}" issues=$(gh issue list --state open --limit 50 --json number,title,author,createdAt,milestone) if [ "$(printf '%s' "$issues" | jq 'length')" -eq 0 ]; then # retry a transient empty (#253) sleep 1; issues=$(gh issue list --state open --limit 50 --json number,title,author,createdAt,milestone) fi total=$(printf '%s' "$issues" | jq 'length') untriaged=$(printf '%s' "$issues" | jq --arg me "$GIT_USER" 'map(select(.author.login != $me)) | map(select(.milestone == null))') echo "Open issues: $total total, $(printf '%s' "$untriaged" | jq 'length') untriaged contributor" printf '%s' "$untriaged" | jq -r '.[] | "#\(.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.
- Report the count line. A
total> 0 with0untriaged contributor issues is only expected when every open issue is the maintainer's or already milestoned; otherwise treat it as a possible dropped-filter miss and re-run. (#253)
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 · 89 lines · 0 tokens per session scan A 19e8ff18db10
merge-and-status is a command published in the GitHub repository LeChabrax/apple-mail-mcp (0 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,562 tokens. A static security scan graded it A with 0 findings. It is 100% identical to merge-and-status, differing in 91 lines, and is treated as a copy.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
handoff
Export a Waybill Bundle by default, or import one when requested.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.