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 vishalvshekkar/app-store-toolkit --skill shipgit clone --depth 1 https://github.com/vishalvshekkar/app-store-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/vishalvshekkar/app-store-toolkit/ship)<a href="https://agentmods.dev/skills/vishalvshekkar/app-store-toolkit/ship"><img src="https://agentmods.dev/badge/skills/vishalvshekkar/app-store-toolkit/ship.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.1 | $0.00060 | $0.01121 |
| Opus 5 | $0.00030 | $0.00561 |
| Sonnet 5 | $0.00012 | $0.00224 |
| Haiku 4.5 | $0.00006 | $0.00112 |
Grade A, and why
app-store-toolkit:ship 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 8d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/app-store-toolkit:ship
You are running a full App Store submission end-to-end. Eight phases; checkpoint after each in .appstore/ship-state.json.
1. Load or initialize ship-state
- Call
store_read_ship_state.- If state exists, this is a resume: skip every phase in
completed_phasesand re-entercurrent_phase. - If no state exists, this is a fresh run: build a fresh
ShipState(schema_version 1, version from config, started_at = now ISO, current_phase = "audit", completed_phases = [], audit_findings_ref = null, waivers = []) and callstore_write_ship_state { state }.
- If state exists, this is a resume: skip every phase in
Parse $ARGUMENTS for --waive check:target (may appear multiple times) and --reason "...". These become the run's waivers.
2. Phases (in order)
Phase 1: audit
- Call
/app-store-toolkit:auditas a sub-skill (or run the audit checks inline). - Read the latest entry from
.appstore/history/audits.jsonl. - For each blocker, check whether it's been waived (the user's
--waivelist matchescheck:target). - If unwaived blockers remain, abort with the punch list and instruction: "Re-run with --waive to override, or resolve the blockers."
- Update ship-state: append
"audit"tocompleted_phases, setcurrent_phase: "push-metadata", setaudit_findings_refto the latest audits.jsonl line index. Persist viastore_write_ship_state.
Phase 2: push-metadata
- Call
/app-store-toolkit:pushwith no asset flag (skip assets; that's phase 6). - On success, update state:
completed_phases += "push-metadata",current_phase = "push-listing".
Phase 3: push-listing
- Push categories, age rating, pricing, availability, encryption (from
listing.json). Use the existing M1 tools (asc_set_categories,asc_set_age_rating,asc_set_pricing,asc_set_availability). - On success, advance state.
Phase 4: push-privacy
asc_set_privacy_responsesfromprivacy.json.- On success, advance state.
Phase 5: push-review
asc_set_review_infofromreview.json.- On success, advance state.
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.
- 8d ago First seen · 90 lines · 60 tokens per session scan A c37a586308bc
app-store-toolkit:ship is a skill published in the GitHub repository vishalvshekkar/app-store-toolkit (5 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 1,121 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
orca-emulator-android
Android device and emulator control from inside Orca over adb, with the live device view in Orca's emulator pane. Use when driving an adb-connected emulator or phone on Windows, Linux, or macOS: booting AVDs, taps, swipes, typing, hardware buttons, rotation, app install and launch, runtime permissions, the…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
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.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.
apple-search-ads
When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT"…
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.