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 glebis/claude-skills --skill app-releasegit clone --depth 1 https://github.com/glebis/claude-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/glebis/claude-skills/app-release)<a href="https://agentmods.dev/skills/glebis/claude-skills/app-release"><img src="https://agentmods.dev/badge/skills/glebis/claude-skills/app-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/glebis/claude-skills/app-release"><img src="https://agentmods.dev/badge/skills/glebis/claude-skills/app-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 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.00166 | $0.01343 |
| Opus 5 | $0.00083 | $0.00672 |
| Sonnet 5 | $0.00033 | $0.00269 |
| Haiku 4.5 | $0.00017 | $0.00134 |
Grade A, and why
app-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 11d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Release (iOS / watchOS → TestFlight / App Store)
Drive an iOS/watchOS app from "production path unstarted" to a Distribution-signed build processing in TestFlight. The hard part is not any single step — it is that the release path spans three disconnected web portals (Apple Developer, App Store Connect, CloudKit Dashboard) plus CLI signing arcana, and each gate hides a silent failure discoverable only after the previous one passes. Treat the whole thing as an airlock checklist: each gate must verifiably seal before the next opens.
When to use
Releasing/publishing/shipping an iOS or watchOS app; getting a build to TestFlight; archiving + uploading; deploying CloudKit schema to Production; filling App Privacy or export compliance; distribution signing; or debugging an Apple upload rejection.
The gates (run in order; verify each before moving on)
Track every gate in the project's issue tracker. Do not assume a gate is closed because a portal shows green — verify the underlying artifact.
- Inventory the gates. List what is actually open (issue tracker, or derive from the steps below). Distinguish gates that block TestFlight from gates that block App Store submission — they are different.
- CloudKit → Production (if the app uses CloudKit). Development indexes/record types do not exist in Production until an explicit Deploy Schema Changes. Deploy via the dashboard and verify the record type appears in the Production environment. One-way action — confirm with the user first.
- Export compliance. Bake
ITSAppUsesNonExemptEncryption: falseinto every shippable target (the app and the watch app), in the source of truth (e.g. XcodeGenproject.ymlinfo.properties), so TestFlight never prompts per build. - App Privacy. Audit the code for analytics / third-party SDKs / external networking first. If the developer cannot access user data (e.g. data lives only in the user's private CloudKit), the honest label is Data Not Collected. Set it in App Store Connect. Leave Publish for submission time.
- Privacy Policy + Impressum. App Store requires a hosted privacy-policy URL; an EU/German operator also needs an Impressum. Add pages to the product site, deploy, paste the privacy URL into App Store Connect.
- Signing audit. With automatic signing, Xcode mints the Distribution cert +
App Store profiles at archive/export — no manual portal work. Confirm the team
id and
CODE_SIGN_STYLE: Automatic. - Archive.
xcodebuild archivethe iPhone scheme that embeds the Watch app,-allowProvisioningUpdates. (Archive signs with Apple Development; the Distribution cert is minted at the export step.) - Export + upload to TestFlight.
xcodebuild -exportArchivewith methodapp-store-connect, automatic signing, and an App Store Connect API key. The key must be Admin role — a Developer-role key cannot cloud-sign and fails with "Cloud signing permission error / no iOS Distribution cert found." - Hand off the device test. The final TestFlight verification (install the processed build, exercise the real feature loop on Production) is a human on-device step. Do not claim it as done.
What ships with it
2 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.
- 11d ago First seen · 89 lines · 166 tokens per session scan A b810c457ebe9
app-release is a skill published in the GitHub repository glebis/claude-skills (374 stars, last pushed 8d ago), licensed MIT. It adds 166 tokens to every session and 1,343 once invoked, about $0.0008 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-30.
Other skills, from other repositories
axiom-shipping
Use when preparing ANY app for submission, handling App Store rejections, writing appeals, or managing App Store Connect. Covers submission checklists, rejection troubleshooting, metadata requirements, privacy manifests, age ratings, export compliance.
asc-ad-hoc-distribution
Prepare, publish, resume, and verify private iOS release-testing installs with asc distribute. Use when distributing an IPA to registered devices outside TestFlight, reconciling ad hoc profiles, publishing through caller-owned S3-compatible storage, or diagnosing a resumable private distribution run.
release-new-version
Use when the user wants to release a new Zafiro version — drafting bilingual release notes, deciding the next version number, bumping app/build.gradle.kts, tagging, and publishing to GitHub (main repo, optionally the Xposed repo).
suede-play-release
Suede Labs Google Play delivery skill: ship an Android release end to end from the agent interface, without opening the Play Console. Set up credentials, upload an AAB, promote between tracks, stage or complete a rollout, push per-locale release notes, and prove against the Play Developer API what is actually live.…
testflight-release
Ship a new TestFlight build of the iOS companion (TermioMobile) — resolve the next build number against App Store Connect, archive, sign, export, upload, write the What to Test notes, and distribute. Invoke when the user says 'ship a testflight build', 'update testflight', 'upload to testflight', 'new beta build'…
gplay-release-flow
End-to-end release workflows for Google Play tracks (internal, beta, production) using gplay release, promote, and rollout commands. Use when asked to upload a build, distribute to testers, or release to production.