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/abdullah4ai/apple-developer-toolkit/asc-testflight-orchestrationnpx skills add Abdullah4AI/apple-developer-toolkit --skill asc-testflight-orchestrationgit clone --depth 1 https://github.com/Abdullah4AI/apple-developer-toolkitWrote 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/abdullah4ai/apple-developer-toolkit/asc-testflight-orchestration)<a href="https://agentmods.dev/skills/abdullah4ai/apple-developer-toolkit/asc-testflight-orchestration"><img src="https://agentmods.dev/badge/skills/abdullah4ai/apple-developer-toolkit/asc-testflight-orchestration.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 | $0.00049 | $0.03131 |
| Opus 5 | $0.00024 | $0.01566 |
| Sonnet 5 | $0.00010 | $0.00626 |
| Haiku 4.5 | $0.00005 | $0.00313 |
Grade A, and why
asc-testflight-orchestration 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 5d 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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release and TestFlight Workflow
Quick path: Adding testers to an existing build
If the user only asks to add/invite a beta tester (NOT build + upload), skip the full workflow. Follow these steps in exact order:
# 1. Check if there are any builds available
asc builds list --app "APP_ID" --limit 3 --output json
If NO builds exist: Tell the user they need to upload a build first. Offer to run the full build+upload workflow (Step 1-9 below). Do NOT add testers without a build.
If builds exist: Continue with external testing below.
Adding a beta tester (external testing)
External testing works for any email — the tester does NOT need to be an App Store Connect team member. However, external testing requires Beta App Review before the tester can install.
# 2. List existing external groups, or create one
asc testflight beta-groups list --app "APP_ID" --output json
asc testflight beta-groups create --app "APP_ID" --name "Beta Testers"
# 3. Assign the latest build to the external group
asc builds add-groups --build "BUILD_ID" --group "GROUP_ID"
# 4. Add the tester to the group (works for any email)
asc testflight beta-testers add --app "APP_ID" --email "[email protected]" --group "Beta Testers"
Now you MUST ask the user for confirmation before submitting for Beta App Review. Say:
"I've added [email protected] to the Beta Testers group. To complete the invitation, this build needs to be submitted for Beta App Review (Apple reviews it, typically < 24 hours). Once approved, the tester will automatically receive a TestFlight invitation email. Shall I submit for Beta App Review?"
Wait for the user's response. Only proceed if they confirm:
# 5. Submit for Beta App Review (only after user confirms)
asc testflight review submit --build "BUILD_ID" --confirm
# 6. Check review status
asc testflight review submissions list --build "BUILD_ID"
Do NOT call asc testflight beta-testers invite for external testers — it will fail with "Tester has no installable build" until Beta App Review is approved. Once approved, the tester automatically receives the invitation.
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.
- 5d ago First seen · 339 lines · 49 tokens per session scan A b60142e8a63f
asc-testflight-orchestration is a skill published in the GitHub repository Abdullah4AI/apple-developer-toolkit (10 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 3,131 once invoked, about $0.0002 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
flutter-cherry-pick
How to land a formal cherry-pick of a merged PR for the flutter/flutter repo stable or beta channel. Only use for flutter/flutter landed pull requests. Only use when the cherry pick request is into "stable", "beta" or a branch that has the format with flutter- . -candidate.0.
engine-whats-new
Generates the "what's new" release summary and diff file for changes in the Flutter engine (//engine/src/flutter) between two releases (e.g., 3.47 vs 3.44). When to use: - Only activate when explicitly asked by the user to generate what's new in the engine, diff Flutter engine releases, or produce an engine release…
release-readiness
Assesses ship-readiness for .NET MAUI release branches — Servicing Releases (SR) and Previews — and produces public-safe, copy-ready release handoffs or Loop-page drafts from the resulting evidence. Use for readiness verdicts, release blockers, Preview/SR status, release handoff pages, manual validation instructions…
find-release
A skill to find the lowest Dart and Flutter release containing a given commit. Use this skill whenever users ask about when a commit landed in Flutter or Dart releases, inquire about release versions for specific SHAs, or want to know if a commit is included in stable, beta, or dev channels for Flutter/Dart projects.
subwave-app-ios-release
Cut a NEW iOS build of the SUB/WAVE app (the Expo project in app/) and ship it via EAS — to TestFlight, and on to the live App Store. The app is LIVE in production on the App Store, so a release is build+submit (one command) then a manual "promote to production" step in App Store Connect. Use this skill whenever the…
release-app
アプリのリリース（バージョンbump + CHANGELOG + タグ → GH Actions で自動ビルド・配布）。iOS / Android / macOS / Linux / Windows の任意の組み合わせでリリースできる。「リリース」「バージョン上げて」「リリースして」と言われたときに使う。.