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 alamops/skills --skill appstore-reviewgit clone --depth 1 https://github.com/alamops/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/alamops/skills/appstore-review)<a href="https://agentmods.dev/skills/alamops/skills/appstore-review"><img src="https://agentmods.dev/badge/skills/alamops/skills/appstore-review/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/alamops/skills/appstore-review"><img src="https://agentmods.dev/badge/skills/alamops/skills/appstore-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 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 43 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 44 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 124 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.00240 | $0.05544 |
| Opus 5.5 | $0.00096 | $0.02218 |
| Sonnet 5.5 | $0.00048 | $0.01109 |
| Haiku 4.5 | $0.00024 | $0.00554 |
Grade A, and why
appstore-review scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Run the bundled fetcher — it downloads the raw pages with `curl`, converts them to text locally, and slices the guidelines per section so every lane gets Apple's exact wording (a summarizing fetch tool paraphrases, and p How it starts
The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Store guideline review
A read-only audit skill: review a project against Apple's live App Store Review Guidelines and the submission requirements Apple publishes around them, and report whether it would survive upload and App Review. Tone: pragmatic reviewer who has shipped apps and knows which rules actually get apps bounced.
Why this skill exists
Apple's rules drift, and they drift in two places. The guidelines themselves change several times a year — in twelve months they gained 2.5.19 (hidden features), 2.3.14 (creative assets), third-party-AI consent in 5.1.2(i), chatbots in 4.7, AI content creation in 1.2, and a United States carve-out for purchase links. And a second set of requirements never appears in the guidelines at all: SDK and deployment-target minimums enforced at upload, the age-rating questionnaire, regional age-assurance laws, and new hardware. When iPhone Duo shipped in October 2026 the guidelines didn't mention it once — the requirements (Duo screenshots mandatory from April 2027, iOS 27 SDK builds that "fail to launch" without the scene life cycle) lived in Apple Developer News and release notes.
Reviewing against a snapshot in the model's head is how teams ship rejections. Pull both sources live, as exact text, at the start of every run. If the guidelines fetch fails, say so plainly and stop — do not guess from training data.
The 6-step workflow
1. Pull the live sources
Run the bundled fetcher — it downloads the raw pages with curl, converts them to text locally, and slices the guidelines per section so every lane gets Apple's exact wording (a summarizing fetch tool paraphrases, and paraphrase is where carve-outs and renumberings get lost):
python3 <skill-dir>/scripts/fetch_sources.py "$TMPDIR/appstore-review"
It writes guidelines.txt, section-1.txt…section-5.txt, news.md (every Apple Developer News item from the last 12 months, full text), upcoming-requirements.txt (minimums in force) and submitting.txt (announced minimums, e.g. the April 2027 SDK and deployment-target floor) outside the repo, and prints the guidelines' Last Updated: date. --rule 5.1.2 prints one rule's exact text — use it to confirm every rule number before it reaches the report. Details, supporting pages to pull per project shape, and the by-hand fallback: references/live-sources.md.
What ships with it
5 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.
- 5d ago Changed · +36 lines · +9 tokens per session fa1ca9302841
- 1mo ago First seen · 205 lines · 231 tokens per session scan A c2286981b231
appstore-review is a skill published in the GitHub repository alamops/skills (52 stars, last pushed 5d ago), licensed MIT. It adds 240 tokens to every session and 5,544 once invoked, about $0.0010 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
play-policy-insights
Automated auditor designed to verify Android applications against Google Play Policy domains. It cross-references static code analysis with Play Store declarations to generate deterministic compliance reports, identifying undeclared data collection, architectural risks, and missing disclosures across Permissions and…
app-store-review
Evaluates code against Apple's App Store Review Guidelines. Use this skill when reviewing iOS, macOS, tvOS, watchOS, or visionOS app code (Swift, Objective-C, React Native, or Expo) to identify potential App Store rejection issues before submission. Triggers on tasks involving app review preparation, compliance…
appstore-review-checker
Audit iOS/macOS apps against App Store Review Guidelines before submission, with evidence-backed verdicts and fixes. Don't use for Google Play, general code review, or rejection appeals.
app-store-preflight-compliance
Pre-submission compliance scanner workflow for Apple App Store apps. Use when reviewing iOS, macOS, tvOS, watchOS, or visionOS projects (Swift, Objective-C, React Native, Expo) for App Store rejection risks, submission readiness, privacy compliance, or guideline violations.
gplay-submission-checks
Pre-submission validation for Google Play releases covering metadata, screenshots, bundle integrity, data safety, and policy compliance. Use when preparing a release to avoid rejections and catch issues before submitting.
privacy-policy
Generate privacy policies, terms of service, and EULAs for Apple platform apps. Detects data collection patterns, third-party SDKs, and generates region-specific legal documents with Apple Privacy Nutrition Label mapping. Use when user needs legal documents or data collection disclosure for App Store submission.