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 SteveGJones/ai-first-sdlc-practices --skill ios-testflight-releasegit clone --depth 1 https://github.com/SteveGJones/ai-first-sdlc-practicesWrote 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/stevegjones/ai-first-sdlc-practices/ios-testflight-release)<a href="https://agentmods.dev/skills/stevegjones/ai-first-sdlc-practices/ios-testflight-release"><img src="https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/ios-testflight-release/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/stevegjones/ai-first-sdlc-practices/ios-testflight-release"><img src="https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/ios-testflight-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 40 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 48 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 58 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00050 | $0.01390 |
| Opus 5 | $0.00025 | $0.00695 |
| Sonnet 5 | $0.00010 | $0.00278 |
| Haiku 4.5 | $0.00005 | $0.00139 |
Grade A, and why
ios-testflight-release 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS TestFlight Release
Get an iOS build onto TestFlight without the classic upload/processing/beta-review blockers. This
skill encodes real incidents (e.g. a build silently never processed because of a missing
NSMotionUsageDescription — ITMS-90683) into a pre-flight → upload → confirm → distribute flow.
Belongs to the ios-release-engineer discipline. Run it before every TestFlight upload; the
config checks are cheap and the failures are expensive (a rejected/stalled upload costs a round-trip).
Arguments
path-to-ios-project— the project directory to check (defaults to the current directory).
Steps
1. Run the pre-flight checks (config that blocks uploads)
Run the bundled checker from the plugin's scripts directory:
python -m ios_preflight.cli <project-dir> [--uses-push]
(Set PYTHONPATH to the plugin's scripts/ dir, or run python plugins/sdlc-team-ios/scripts/ -m ios_preflight.cli from a checkout.) It reports, and you must resolve every ERROR before uploading:
- Missing usage descriptions — every sensitive framework the app links/uses needs its
NS…UsageDescriptionpurpose string, or App Store Connect rejects the build in processing (ITMS-90683). The check maps frameworks to keys (CoreMotion→NSMotionUsageDescription, AVFoundation→NSCameraUsageDescription, CoreLocation→NSLocationWhenInUseUsageDescription, Contacts, Photos, Speech, HealthKit, …). Rule of thumb: if a permission dialog could appear, the string must exist — and be a real human sentence (Apple rejects placeholder text). - Export compliance — set
ITSAppUsesNonExemptEncryption = falsein Info.plist if the app uses only exempt encryption (standard HTTPS). This skips the export-compliance questionnaire on every upload; without it each build stalls waiting for an answer in ASC. - Privacy manifest — add a
PrivacyInfo.xcprivacyif you use required-reason APIs (UserDefaults, file/disk timestamps, system boot time, disk space) or bundle third-party SDKs; Apple flags builds without it. - Entitlements — no
get-task-allowin a release build;aps-environment = productionfor push.
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 · 102 lines · 50 tokens per session scan A be3a512371f1
ios-testflight-release is a skill published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 1,390 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-09-03.
Other skills, from other repositories
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
eas-simulator
EAS service (paid). Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any eas simulator: commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas…
test-native-extension
Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCTEXPORTMETHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg…