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 Dev869/swift-tothemax --skill apple-release-opsgit clone --depth 1 https://github.com/Dev869/swift-tothemaxWrote 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/dev869/swift-tothemax/apple-release-ops)<a href="https://agentmods.dev/skills/dev869/swift-tothemax/apple-release-ops"><img src="https://agentmods.dev/badge/skills/dev869/swift-tothemax/apple-release-ops.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.00215 | $0.02914 |
| Opus 5 | $0.00108 | $0.01457 |
| Sonnet 5 | $0.00043 | $0.00583 |
| Haiku 4.5 | $0.00021 | $0.00291 |
Grade A, and why
apple-release-ops 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apple Release Ops
You own the pipeline: signed binary → TestFlight → App Store → monitored release. As of July
2026: Xcode 26.6 (Swift 6.3, iOS 26.5 SDK, requires macOS Tahoe 26.2+). Sibling skills own
review strategy (app-review-max) and legal/compliance (apple-legal-max) — route there, don't
improvise.
Signing, demystified
Four artifacts, four jobs. Most "signing hell" is conflating them:
| Artifact | What it is | Where it lives |
|---|---|---|
| Certificate | Your identity (public key signed by Apple + your private key) | Keychain. Private key is the part you can lose. |
| Provisioning profile | Apple's permission slip: this cert + this app ID + these entitlements (+ these devices, for dev/ad-hoc) | ~/Library/Developer/Xcode/UserData/Provisioning Profiles/ (Xcode 16+; formerly ~/Library/MobileDevice/) |
| Entitlements | Key-value claims baked into the binary at sign time (.entitlements file) |
Inside the signed binary. Inspect: codesign -d --entitlements - MyApp.app |
| Capability | App Store Connect / Xcode UI switch that regenerates the app ID config and profiles | Developer portal |
Rules that resolve 90% of confusion:
- Every entitlement your binary claims MUST be allowed by the profile it ships with. Mismatch = install/upload failure, not a build failure.
- Distribution profiles have no device list. "Device not registered" is a development/ad-hoc problem only.
- Cloud-managed certificates (Xcode 13+, default with automatic signing + "Distribute App"):
Apple holds the distribution private key. Nothing to back up, nothing to expire out from under
you, works with
xcodebuild -allowProvisioningUpdates. Prefer them unless your CI can't authenticate to Apple.
Decision: automatic vs manual signing.
- Solo dev / small team, Xcode or Xcode Cloud builds → automatic + cloud-managed certs. Done.
- Self-hosted CI, multiple apps sharing certs, or extensions with exotic entitlements →
manual with profiles checked into a secrets store, or fastlane
match(git/S3-backed, encrypted). Never both: mixed automatic/manual across targets is the #1 source of phantom errors. - Wrong: fixing CI signing by exporting your personal dev certificate. Right: a dedicated distribution cert (or cloud signing via App Store Connect API key) that no laptop depends on.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 204 lines · 215 tokens per session scan A 1a6153839da4
apple-release-ops is a skill published in the GitHub repository Dev869/swift-tothemax (7 stars, last pushed 2mo ago), licensed MIT. It adds 215 tokens to every session and 2,914 once invoked, about $0.0011 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-08-31.
Other skills, from other repositories
apple-app-delivery
Upload builds, distribute on TestFlight, manage metadata, submit for Beta/App Review, and release on the App Store using Apple's official CLIs and the App Store Connect API. Default stable delivery to APPSTORE so one build can be tested in TestFlight and later submitted to the App Store; choose TESTFLIGHTINTERNALONLY…
app-store-review-guidelines
Route App Store submission-compliance tasks to the correct Knowledge Contracts — app completeness, demo accounts, screenshot/description accuracy, in-app purchase requirements, external payment link restrictions, restore purchases, minimum functionality, spam/duplicate-app avoidance, permission usage strings, privacy…
backgroundtasks
Route BackgroundTasks implementation tasks to the correct Knowledge Contracts -- background task registration and scheduling, task execution and expiration handling, processing task constraints and conditions, and background refresh and widget timeline hookup. Use when registering a task identifier with…
core-data
Route Core Data implementation tasks to the correct Knowledge Contracts -- subclassing NSManagedObject and choosing an .xcdatamodeld Codegen mode (Class Definition/Manual-None/Category+Extension) with @NSManaged properties, standing up NSPersistentContainer via loadPersistentStores(completionHandler:) and viewContext…
core-location
Route Core Location implementation tasks to the correct Knowledge Contracts -- authorization and usage strings, location updates and delivery, accuracy and precise location, and background monitoring with location-triggered launches. Use when reading CLAuthorizationStatus or authorizationStatus, calling…
networking
Route URLSession networking implementation tasks to the correct Knowledge Contracts — request construction, async/await and completion-handler data fetching, Codable decoding, HTTP error handling, task cancellation, session configuration, App Transport Security, authenticated requests, session delegates and their…