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 agentmods add skills/moasq/ios-dev-agent/apple-developer-authnpx skills add moasq/ios-dev-agent --skill apple-developer-authgit clone --depth 1 https://github.com/moasq/ios-dev-agentWhat 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 | $0.00050 | $0.00761 |
| Opus 5 | $0.00025 | $0.00380 |
| Sonnet 5 | $0.00010 | $0.00152 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
apple-developer-auth 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 2d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apple Developer Authentication
Tell the user to run the interactive menu:
! python3 .agents/scripts/apple-developer-auth.py
What the menu shows
If not connected (red):
● Not connected
[1] Sign in (Apple ID + password + 2FA)
[2] Manual (provide .p8 API key for asc CLI)
If connected (green):
● Connected as [email protected]
Session age: 3d — valid for ~27d more
[1] Revoke session (sign out)
[2] List apps
[3] List certificates
[4] List profiles
[5] Register bundle ID
[6] Setup asc CLI (.p8 key)
If expired (yellow):
● Expired session for [email protected]
[1] Sign in
[2] Manual
[3] Revoke (clear expired session)
Direct commands
For non-interactive use (e.g. from Claude):
# Sign in
! python3 .agents/scripts/apple-developer-auth.py login --user [email protected]
# Check status (validates live against Apple)
! python3 .agents/scripts/apple-developer-auth.py status
# Revoke / sign out
! python3 .agents/scripts/apple-developer-auth.py revoke
# Portal operations
! python3 .agents/scripts/apple-developer-auth.py list-apps
! python3 .agents/scripts/apple-developer-auth.py list-certs
! python3 .agents/scripts/apple-developer-auth.py list-profiles
! python3 .agents/scripts/apple-developer-auth.py register-bundle com.example.app "My App"
# Manual .p8 key setup
! python3 .agents/scripts/apple-developer-auth.py setup-asc
Auth flow internals (mirrors Fastlane Spaceship)
- Widget key from
appstoreconnect.apple.com/olympus/v1/app/config - Hashcash proof-of-work (SHA-1,
X-Apple-HC-Bits/X-Apple-HC-Challenge) - SRP-6a:
signin/init(sends A, receives B+salt+iterations) → PBKDF2 →signin/complete(sends M1+M2) - 2FA: device push or SMS (user types code, or
smsto switch) - Trust:
GET /appleauth/auth/2sv/trust - Cookies persisted at
~/.apple-developer-auth/cookies.txt(~30 days)
Status validation
status and menu validate live — not just checking if a cookie file exists. They call Apple's Olympus session endpoint and report:
- Green (valid): Cookie exists AND Apple accepted it
- Yellow (expired): Cookie exists but Apple rejected it
- Red (not connected): No session at all
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.
- 2d ago First seen · 91 lines · 50 tokens per session scan A 89e9f546b014
apple-developer-auth is a skill published in the GitHub repository moasq/ios-dev-agent (4 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 761 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…