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 agentmods add commands/eddiebelaval/squire/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/commands/eddiebelaval/squire/appstore-readiness)<a href="https://agentmods.dev/commands/eddiebelaval/squire/appstore-readiness"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/appstore-readiness.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.00000 | $0.01112 |
| Opus 5 | $0.00000 | $0.00556 |
| Sonnet 5 | $0.00000 | $0.00222 |
| Haiku 4.5 | $0.00000 | $0.00111 |
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 6d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/appstore-readiness - Full App Store Readiness Audit
Purpose
Run a comprehensive App Store readiness audit before submission. This command invokes all specialized agents to ensure your iOS app is ready for first-submission approval.
When to Use
- Before submitting a new app to the App Store
- Before submitting a major update
- At ID8Pipeline Stage 9 (Launch Prep) as a hard gate
- When you want a complete compliance check
Workflow
Phase 1: Technical Audit
TECHNICAL Agent:
- Verify Xcode/SDK version compliance
- Check device compatibility declarations
- Review Info.plist for required keys
- Validate build configuration
- Check for deprecated APIs
Output: Technical readiness status with any blocking issues.
Phase 2: Privacy Audit
PRIVACY Agent:
- Scan for privacy manifest (PrivacyInfo.xcprivacy)
- Verify all collected data types declared
- Check required reason APIs are justified
- Review third-party SDK privacy compliance
- Validate ATT implementation (if tracking)
- Cross-reference privacy labels
Output: Privacy compliance status with specific findings.
Phase 3: Design Audit
DESIGNER Agent:
- Review navigation patterns against HIG
- Check touch target sizes
- Verify Dynamic Type support
- Assess Dark Mode implementation
- Check accessibility compliance
Output: HIG compliance status with recommendations.
Phase 4: Monetization Audit (if applicable)
COMMERCE Agent:
- Determine if IAP is required
- Review IAP implementation
- Check subscription sign-up requirements
- Verify pricing display
- Confirm restore purchases functionality
Output: Monetization compliance status.
Phase 5: Metadata Audit
METADATA Agent:
- Review app name (≤30 chars, no keyword stuffing)
- Audit screenshots (correct sizes, app in use)
- Check description accuracy
- Validate age rating
- Confirm support URL accessibility
Output: Metadata readiness status with improvements.
Phase 6: Review Simulation
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.
- 6d ago First seen · 166 lines · 0 tokens per session scan A 249a8b4b6b02
appstore-readiness is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,112 tokens. 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 commands, from other repositories
f5-mobile
Mobile development commands.
gradle-build
Fix Gradle build errors for Android and KMP projects.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
initialize-ios
Manual override: initialize ast-index for iOS/Swift/ObjC project.
flutter-test
Run Flutter/Dart tests, report failures, and incrementally fix test issues. Covers unit, widget, golden, and integration tests.
note
Zero-friction idea capture. Append, list, or promote notes to todos.