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 eddiebelaval/squire --skill appstore-readinessgit clone --depth 1 https://github.com/eddiebelaval/squireWrote 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/eddiebelaval/squire/appstore-readiness)<a href="https://agentmods.dev/skills/eddiebelaval/squire/appstore-readiness"><img src="https://agentmods.dev/badge/skills/eddiebelaval/squire/appstore-readiness/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/eddiebelaval/squire/appstore-readiness"><img src="https://agentmods.dev/badge/skills/eddiebelaval/squire/appstore-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00102 | $0.06234 |
| Opus 5 | $0.00051 | $0.03117 |
| Sonnet 5 | $0.00020 | $0.01247 |
| Haiku 4.5 | $0.00010 | $0.00623 |
Grade A, and why
appstore-readiness 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 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.
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 — 914 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core Workflows
Workflow 1: Primary Action
- Analyze the input and context
- Validate prerequisites are met
- Execute the core operation
- Verify the output meets expectations
- Report results
REVIEWER — Compliance Auditor
Expertise: Former App Review Team member with 10+ years reviewing apps across all categories
Purpose: Audit apps against ALL App Store Review Guidelines before submission. Think like a reviewer. Catch rejection triggers before Apple does.
Behavior Protocol
-
Systematic Section Check:
- Section 1: Safety (objectionable content, UGC, kids, physical harm)
- Section 2: Performance (completeness, metadata, compatibility)
- Section 3: Business (payments, monetization, spam)
- Section 4: Design (copycats, minimum functionality, extensions)
- Section 5: Legal (privacy, IP, gambling)
-
Flag Specific Guidelines:
- Always cite the exact guideline number (e.g., "Guideline 2.3.7")
- Explain what the guideline requires
- Show how the app violates or complies
-
Rejection Probability Assessment:
- 🔴 HIGH RISK — Almost certain rejection, must fix
- 🟡 MEDIUM RISK — Likely rejection, strongly recommend fix
- 🟢 LOW RISK — Minor concern, consider addressing
- ✅ CLEAR — Compliant, no issues detected
-
Generate Pre-Submission Report:
┌─────────────────────────────────────────┐ │ PRE-SUBMISSION AUDIT REPORT │ ├─────────────────────────────────────────┤ │ App: [Name] │ │ Date: [Date] │ │ Overall Risk: [HIGH/MEDIUM/LOW/CLEAR] │ ├─────────────────────────────────────────┤ │ BLOCKING ISSUES (Must Fix) │ │ • [Issue] — Guideline X.X.X │ ├─────────────────────────────────────────┤ │ WARNINGS (Should Fix) │ │ • [Issue] — Guideline X.X.X │ ├─────────────────────────────────────────┤ │ RECOMMENDATIONS │ │ • [Suggestion] │ └─────────────────────────────────────────┘
What ships with it
11 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.
- CLAUDE.md 8.1 KB
- README.md 6.0 KB
- references/app-store-review-guidelines.md 12 KB
- references/common-rejection-reasons.md 12 KB
- references/human-interface-guidelines.md 10 KB
- references/in-app-purchase-rules.md 11 KB
- references/pre-submission-checklist.md 9.2 KB
- references/privacy-requirements.md 12 KB
- references/screenshot-metadata-specs.md 11 KB
- references/subscription-guidelines.md 13 KB
- references/technical-requirements.md 12 KB
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 First seen · 914 lines · 102 tokens per session scan A a31c39c5ce53
appstore-readiness is a skill published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 23d ago), licensed MIT. It adds 102 tokens to every session and 6,234 once invoked, about $0.0005 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-09-03.
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_remix
Create a new Rome app from an App Store source, already installed or identified by a pinned Store version. Copy installed code locally or download and extract a Store bundle without installing the source. Never edit or overwrite an existing source app.
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…
account-deletion
Generates an Apple-compliant account deletion flow with multi-step confirmation UI, optional data export, configurable grace period, Keychain cleanup, and server-side deletion request. Use when user needs account deletion, right-to-delete, or Apple App Review compliance for account removal.
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.
appstore-review
(alamops) Use whenever the user wants their iOS app checked against Apple's App Store Review Guidelines, or asks if Apple will reject something. Triggers — "check this against the app store guidelines", "will Apple reject this?", pre-submission audit, App Store readiness, pre-flight before TestFlight or App Store…