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 cruisediary/apple-app-review-skills --skill app-completeness-checkgit clone --depth 1 https://github.com/cruisediary/apple-app-review-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/cruisediary/apple-app-review-skills/app-completeness-check)<a href="https://agentmods.dev/skills/cruisediary/apple-app-review-skills/app-completeness-check"><img src="https://agentmods.dev/badge/skills/cruisediary/apple-app-review-skills/app-completeness-check/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/cruisediary/apple-app-review-skills/app-completeness-check"><img src="https://agentmods.dev/badge/skills/cruisediary/apple-app-review-skills/app-completeness-check.svg" alt="Reviewed on agentmods" width="80" 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.00038 | $0.01976 |
| Opus 5.5 | $0.00015 | $0.00790 |
| Sonnet 5.5 | $0.00008 | $0.00395 |
| Haiku 4.5 | $0.00004 | $0.00198 |
Grade A, and why
app-completeness-check 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 1mo 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: App Completeness Check
Purpose
Detects placeholder content, stub UI, hardcoded test credentials, and non-production endpoints that signal an incomplete app to reviewers under Guideline 2.1.
Apple Guideline
- Primary: 2.1 — Performance: App Completeness
- Related: 2.3, 4.2 — Design: Minimum Functionality
- Reference:
references/guidelines/2-performance.md
Real-World Rejection Cases
-
Case: "Lorem ipsum" text found in production build by App Store reviewer — rejected under 2.1 Source: decode.agency/article/app-store-rejection/ Root cause: Placeholder content in final submission is treated as incomplete app — reviewers actively look for this and it is a clear rejection signal
-
Case: App with greyed-out "Coming Soon" tab visible to reviewer — rejected Source: Multiple developer blogs Root cause: Unimplemented features visible to reviewer signal incomplete app — if a feature is not ready, it must not be visible in the submitted build
-
Case: Support URL in App Store Connect returning 404 — rejected Source: mobiloud.com/blog/avoid-app-rejected-apple Root cause: All URLs in metadata must be functional at review time — broken support links are checked by reviewers
-
Case: App required account creation before any feature was accessible, with no guest or explore mode — reviewer had no way to evaluate core functionality without signing up — rejected under Guideline 2.1 Source: Purchasely (purchasely.com/blog/app-store-rejection-reasons) Root cause: Guideline 2.1 requires reviewers to be able to access and evaluate the app's core functionality; mandatory registration with no bypass blocks review entirely — provide a demo account or guest mode
Trigger
Invoke on any iOS/macOS project before App Store submission to catch completeness issues that commonly cause rejection.
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.
- 1mo ago First seen · 149 lines · 38 tokens per session scan A aecca4c2663d
app-completeness-check is a skill published in the GitHub repository cruisediary/apple-app-review-skills (19 stars, last pushed 6mo ago), licensed MIT. It adds 38 tokens to every session and 1,976 once invoked, about $0.0002 per session on Opus 5.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-05.
Other skills, from other repositories
cli-anything-nslogger
CLI harness for NSLogger — parse, filter, export, and monitor NSLogger log files (.rawnsloggerdata / .nsloggerdata).
benchmark
Run performance + quality benchmarks. ASR reports WER, RTF, process memory, and throughput across engines/variants. Arguments include asr, tts, vad, diarize, asr-quick.
review-pr
Review a pull request for conceptual fit, architecture impact, adversarial failure modes, security risk, docs impact, regression risk, test coverage, and merge readiness. Use when asked to review a PR, check whether a PR is safe to merge, decide if more tests are needed, perform adversarial or security review, or…
swift-expert
Expert-level Swift development for iOS, macOS with SwiftUI, Combine, and modern Swift 5.9+. Use when the user mentions iOS, macOS, SwiftUI, Combine, async await, or Apple platforms, or when the task involves Modern Swift Features, Basics and Optionals, Functions and Closures, or Structs and Classes.
boutique-best-practices
Best practices for using Boutique with Swift 6 concurrency, @Observable, @ObservationIgnored, Sendable conformance, testing with preview stores, and dependency injection. Use when troubleshooting Boutique issues, migrating to Swift 6, or setting up tests.
boutique-store
Create and use Boutique Store for Swift data persistence, including initialization, @Stored controllers, CRUD operations, operation chaining, and granular event monitoring. Use when persisting arrays of items, building data controllers, or working with Boutique's Store type.