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.
git 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-submit)<a href="https://agentmods.dev/commands/eddiebelaval/squire/appstore-submit"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/appstore-submit/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/commands/eddiebelaval/squire/appstore-submit"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/appstore-submit.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.00000 | $0.00960 |
| Opus 5.5 | $0.00000 | $0.00384 |
| Sonnet 5.5 | $0.00000 | $0.00192 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
appstore-submit 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/appstore-submit - App Store Submission Guide
Purpose
Step-by-step guide through the App Store submission process. Uses SENTINEL for timing and FIXER if issues arise.
Prerequisites
Before using this command, ensure:
-
/appstore-readinessaudit passed - ID8Pipeline Stage 9 checkpoint cleared
- All blocking issues resolved
Submission Workflow
Step 1: Pre-Submission Verification
SENTINEL Agent checks:
- Optimal submission timing
- Holiday freeze status
- Expected review time
- Any known App Review issues
Step 2: App Store Connect Preparation
Checklist:
App Store Connect → My Apps → [Your App]
PREPARE FOR SUBMISSION:
□ Version number correct
□ Build uploaded and selected
□ App Information complete
□ App name
□ Subtitle
□ Privacy Policy URL
□ Category
□ Pricing and Availability
□ Price tier set
□ Availability selected
□ App Privacy
□ Privacy labels complete
□ All data types identified
□ App Review Information
□ Contact information
□ Demo account (if needed)
□ Notes for reviewers
□ Version Information
□ What's New text
□ Screenshots uploaded
□ App Preview (optional)
□ Promotional text (optional)
Step 3: Demo Account Setup
If app requires login:
Demo Account Information:
─────────────────────────
Username: [your-demo-email]
Password: [your-demo-password]
Notes for Reviewer:
• Full access to all features
• No 2FA required
• Account won't expire
• [Any special instructions]
Step 4: Review Notes
Template:
App Review Notes
────────────────
DEMO ACCOUNT:
Username: [email protected]
Password: AppReview2025!
Access: Full premium features
TESTING INSTRUCTIONS:
• [Feature 1]: [How to access/test]
• [Feature 2]: [How to access/test]
• [Any hardware requirements]
SPECIAL NOTES:
• [Anything unusual about the app]
• [Features that might not be obvious]
• [Permissions explained]
Step 5: Final Checks
Before clicking Submit:
- Test demo account one more time
- Verify backend services are running
- Check all metadata for typos
- Confirm screenshots are current
- Review pricing settings
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 · 189 lines · 0 tokens per session scan A 18aba8f79dc3
appstore-submit is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 960 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.
erne-animate
ERNE — Implement animations using the ui-designer agent with Reanimated and Gesture Handler.
react-native
Command "react-native" from getsentry/toolkit, covering examples, also associate with a release and distribution(s), xcode build step (react-native xcode) and important notes.
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…
qos-forge
Design a multi-agent team with Qualixar OS Forge. Provide a task description, Forge picks the topology, agents, and tools.