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 Xopoko/build-swift-apps --skill appstore-release-directorgit clone --depth 1 https://github.com/Xopoko/build-swift-appsWrote 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/xopoko/build-swift-apps/appstore-release-director)<a href="https://agentmods.dev/skills/xopoko/build-swift-apps/appstore-release-director"><img src="https://agentmods.dev/badge/skills/xopoko/build-swift-apps/appstore-release-director/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/xopoko/build-swift-apps/appstore-release-director"><img src="https://agentmods.dev/badge/skills/xopoko/build-swift-apps/appstore-release-director.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 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 14 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 17 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.00045 | $0.00776 |
| Opus 5 | $0.00023 | $0.00388 |
| Sonnet 5 | $0.00009 | $0.00155 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
appstore-release-director 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Store Release Director
Broad release orchestration. For focused asc work, delegate to appstore-connect-cli, appstore-id-resolver, appstore-archive-uploader, appstore-release-planner, appstore-review-readiness, appstore-metadata-sync, appstore-metadata-localizer, appstore-screenshot-pipeline, and appstore-signing-setup.
Workflow
- Discover release truth:
- git root, workspace/project, scheme, bundle ID, version/build, deployment target, entitlements, generator ownership;
- existing handoff/docs:
apple-publishing-handoff.md, manifest JSON,release,appstore,testflight,fastlane,ExportOptions.plist.
- Verify Apple account/signing:
- team, Team ID, API key, identities, Bundle ID resource/capabilities, distribution cert, provisioning profile;
- keep
.p8,.p12, profiles, passwords, and decoded plists out of git; prefer.codex-private/apple/or a secret store.
- Prepare App Store Connect:
- app record, platform, bundle, app info, categories, pricing/availability, age rating, privacy/support URLs, screenshots, App Privacy, review details, release option;
- for subscriptions, verify products and Terms/EULA link. Standard EULA:
https://www.apple.com/legal/internet-services/itunes/dev/stdeula/.
- Compliance preflight:
- production runtime config, legal URLs return 2xx/3xx, encryption/export compliance, privacy/tracking claims match code/SDKs.
- Build/test/archive/export/upload:
- choose unique build number from live ASC state;
- run required tests/smoke checks;
- archive for
generic/platform=iOS, export App Store IPA, validate, upload, wait for processing.
- Link build and submit/readiness:
- attach processed build, resolve metadata-only issues before new binaries, cancel/complete old submissions if blocking.
- Finish evidence:
- handoff/manifest: version/build, archive/IPA paths, SHA-256, delivery UUID, ASC build state, review submission ID, legal URLs, screenshots, remaining risks.
What ships with it
9 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.
- agents/openai.yaml 329 B
- references/app-store-connect-api.md 4.1 KB
- references/build-upload-submit.md 5.1 KB
- references/end-to-end-workflow.md 4.6 KB
- references/metadata-compliance.md 4.7 KB
- references/signing-and-provisioning.md 3.7 KB
- references/troubleshooting.md 4.0 KB
- scripts/appstore_preflight.py 5.6 KB runs code
- scripts/make_export_options.py 2.0 KB runs code
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 · 62 lines · 45 tokens per session scan A 15e1e89b8927
appstore-release-director is a skill published in the GitHub repository Xopoko/build-swift-apps (45 stars, last pushed 14d ago), licensed MIT. It adds 45 tokens to every session and 776 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-30.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…
skillshare-release
End-to-end release workflow for skillshare. Runs tests, generates changelog (via /changelog), optionally writes local RELEASENOTES, updates version numbers, commits, and drafts announcements. Use when the user says "release", "prepare release", "cut a release", "release v0.19", or any request to publish a new version.…
github-release-briefing-skill
Create a source-linked briefing for the latest published GitHub release of a public repository. Use for engineering teams tracking a dependency release; do not use it to publish releases or change 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.