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.
npx skills add markdavidgan/apple-dev-skills --skill merge-checkgit clone --depth 1 https://github.com/markdavidgan/apple-dev-skillsWrote 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/skills/markdavidgan/apple-dev-skills/merge-check)<a href="https://agentmods.dev/skills/markdavidgan/apple-dev-skills/merge-check"><img src="https://agentmods.dev/badge/skills/markdavidgan/apple-dev-skills/merge-check/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/skills/markdavidgan/apple-dev-skills/merge-check"><img src="https://agentmods.dev/badge/skills/markdavidgan/apple-dev-skills/merge-check.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.00096 | $0.01864 |
| Opus 5 | $0.00048 | $0.00932 |
| Sonnet 5 | $0.00019 | $0.00373 |
| Haiku 4.5 | $0.00010 | $0.00186 |
Grade A, and why
merge-check 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 6d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge Check Skill
Pre-merge quality gate with parallel verification.
Auto-Triggers
This skill activates when you say:
- "Merge this to main"
- "Is this ready to merge?"
- "Create a pull request"
- "Check if I can merge"
- "Verify this branch"
Parallel Subagent Architecture
Instead of running checks sequentially, spawn 4 subagents in parallel:
┌─────────────────────────────────────────────────────────────┐
│ Merge Check Orchestrator │
│ (You) │
└──┬──────────────┬──────────────────┬──────────────┬─────────┘
│ │ │ │
┌──▼──────┐ ┌────▼─────┐ ┌────────▼───┐ ┌──────▼────────┐
│ Build │ │ Archive │ │ Test │ │ Lint │
│ • Debug │ │ • Release│ │ • Unit │ │ • SwiftLint │
│ • Watch │ │ • Strict │ │ • UI (fast)│ │ • Debug code │
│ • Check │ │ concur.│ │ • Coverage │ │ • Isolation │
└─────────┘ └──────────┘ └────────────┘ └───────────────┘
CRITICAL: The Archive subagent catches strict concurrency errors that simulator builds miss. This is the #1 cause of Xcode Cloud failures.
Don't wait for merge to run archive. For any session touching Swift concurrency, MainActor, or new services, run a release archive build during development — not just here. Fixing archive errors while the code is fresh is 10x faster than fixing them at merge time.
Workflow
Phase 1: Context Analysis (You)
- Detect current branch
- Check if behind main
- Determine changed files
- Spawn 4 subagents in parallel
Phase 2: Parallel Verification (Subagents)
Subagent 1: Build Verification
Task: Verify debug builds compile
Inputs: Branch name, changed files
Outputs: Build status, error count, first 10 errors
Commands: Use your project's build commands (xcodebuild, swift build, etc.)
Subagent 2: Archive Verification (catches Xcode Cloud failures)
Task: Run release archive builds to catch strict concurrency errors
Inputs: Branch name, changed targets
Outputs: Archive status, concurrency/isolation errors
Note: Debug simulator builds do NOT catch MainActor isolation errors.
Archive builds use -O optimization which enforces strict concurrency.
This is the #1 reason Xcode Cloud archives fail.
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.
- 6d ago First seen · 216 lines · 96 tokens per session scan A deef43c769d4
merge-check is a skill published in the GitHub repository markdavidgan/apple-dev-skills (5 stars, last pushed 10d ago), licensed MIT. It adds 96 tokens to every session and 1,864 once invoked, about $0.0005 per session on Opus 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-03.
Other skills, from other repositories
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
asc-shots-pipeline
Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (asc screenshots frame), and screenshot upload (asc screenshots upload). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition…
asc-ad-hoc-distribution
Prepare, publish, resume, and verify private iOS release-testing installs with asc distribute. Use when distributing an IPA to registered devices outside TestFlight, reconciling ad hoc profiles, publishing through caller-owned S3-compatible storage, or diagnosing a resumable private distribution run.
Changelog Test Mapper
Map changelog entries and release notes to affected test cases, ensuring every user-facing change has corresponding test coverage verification.
gate
MANDATORY before every commit and push. All gates must pass — Gates 1–3 always run; Gates 4 (Docker) and 5 (Cloud) run only when applicable. Do NOT proceed if any gate fails — fix the issue first.
am-command-build
Implement the next task incrementally — build, test, verify, commit.