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 ios-buildgit 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/ios-build)<a href="https://agentmods.dev/skills/markdavidgan/apple-dev-skills/ios-build"><img src="https://agentmods.dev/badge/skills/markdavidgan/apple-dev-skills/ios-build.svg" alt="Measured on agentmods" 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.00094 | $0.07041 |
| Opus 5 | $0.00047 | $0.03521 |
| Sonnet 5 | $0.00019 | $0.01408 |
| Haiku 4.5 | $0.00009 | $0.00704 |
Grade C, and why
ios-build scanned grade C with 1 finding 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
code or `rm -rf` the cache reflexively.** Confirm with `pgrep -f "xcodebuild|swift-frontend"` first. How it starts
The opening of the file, as written. The whole thing — 845 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS Build
Build system patterns, validation workflows, and troubleshooting. Run validation before every commit.
The 4-Layer Validation Pipeline
Use the lightest layer that matches your situation.
| Layer | Command | Time | What It Catches |
|---|---|---|---|
| 1. Fast | make validate-fast |
~30s | Lint, isolation violations, safety patterns |
| 2. Full | make validate |
~3 min | Layer 1 + archive builds (Swift 6 strict concurrency) |
| 3. Export Test | make export-test-{app} |
~5 min | Layer 2 + signing, provisioning, icons, entitlements |
| 4. Upload | bundle exec fastlane alpha |
~10 min | Layer 3 + Apple Transporter, TestFlight processing |
When to Use Each Layer
- During development:
make validate-fastafter each significant change - Before committing:
make validateat minimum - Before pushing:
make export-test-{app}for the affected app(s) - Release:
bundle exec fastlane alphato upload
Critical Rule: Archive vs Debug Builds
Debug/simulator builds do NOT catch all strict concurrency errors.
Swift 6 strict concurrency checking is more thorough in optimized builds:
# Debug build — misses some concurrency errors
xcodebuild -scheme MyApp -destination 'platform=iOS Simulator,name=iPhone 17 Pro Max' build
# Archive build — catches ALL concurrency errors
xcodebuild -scheme MyApp -destination 'generic/platform=iOS' archive
Always run archive builds before committing Swift code changes.
XcodeGen
Project Structure
# project.yml
name: MyApp
targets:
MyApp-iOS:
type: application
platform: iOS
deploymentTarget: "26.0"
sources:
- MyApp-iOS
dependencies:
- target: MyAppKit
- sdk: HealthKit.framework
- sdk: Speech.framework
settings:
base:
SWIFT_STRICT_CONCURRENCY: complete
SWIFT_DEFAULT_ACTOR_ISOLATION: MainActor
PRODUCT_BUNDLE_IDENTIFIER: com.example.myapp
info:
path: MyApp-iOS/Info.plist
properties:
UISupportedInterfaceOrientations: [UIInterfaceOrientationPortrait]
MyAppKit:
type: framework
platform: iOS
sources:
- MyAppKit/Sources
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.
- 4d ago First seen · 845 lines · 94 tokens per session scan C 56325f2be3bd
ios-build is a skill published in the GitHub repository markdavidgan/apple-dev-skills (5 stars, last pushed 8d ago), licensed MIT. It adds 94 tokens to every session and 7,041 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
asc-revenuecat-catalog-sync
Reconcile App Store Connect subscriptions and in-app purchases with RevenueCat products, entitlements, offerings, and packages using asc and RevenueCat MCP. Use when setting up or syncing subscription catalogs across ASC and RevenueCat.
asc-localize-metadata
Automatically translate and sync App Store metadata (description, keywords, what's new, subtitle) to multiple languages using LLM translation and asc CLI. Use when asked to localize an app's App Store listing, translate app descriptions, or add new languages to App Store Connect.
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-metadata-sync
Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.
asc-release-flow
Orchestrate App Store releases with asc, including staging a version, uploading or building an artifact, publishing, and submitting for review. Use when the user wants to prepare or execute a release. Keep Game Center item preparation in this skill; route other readiness failures, stuck submissions, cancellation, and…
asc-submission-health
Diagnose App Store submission blockers and operate review health with asc, including readiness validation, repair routing, status monitoring, cancellation, and retry decisions. Use when validation fails, a version is not in a valid state, review status is unclear or stuck, or a failed submission must be repaired and…