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/carolanelfbv/ios-development-agents/publishgit clone --depth 1 https://github.com/CarolaneLFBV/ios-development-agentsWrote 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/carolanelfbv/ios-development-agents/publish)<a href="https://agentmods.dev/commands/carolanelfbv/ios-development-agents/publish"><img src="https://agentmods.dev/badge/commands/carolanelfbv/ios-development-agents/publish.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 | $0.00006 | $0.00472 |
| Opus 5 | $0.00003 | $0.00236 |
| Sonnet 5 | $0.00001 | $0.00094 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
publish 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 4d 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.
What it actually says
/ios:publish - App Store Publishing
Prepare app for App Store submission: $ARGUMENTS.
Delegation
Executed by the devops-specialist. Spawn it via the Task tool for build validation, signing, screenshots, and App Store Connect metadata.
Arguments
| Flag | Values | Default | Description |
|---|---|---|---|
--validate |
- | - | Validate build for submission |
--screenshots |
- | - | Generate App Store screenshots |
--metadata |
- | - | Prepare App Store metadata |
--export |
- | - | Export IPA for submission |
Pre-Submission Checklist
App Store Guidelines
- Content guidelines compliance
- Privacy policy URL
- Data collection disclosure
- Age rating accurate
Technical Requirements
- App icons (all sizes)
- Launch screen
- iOS version compatibility
- Device compatibility
Metadata
- App description
- Keywords (100 chars)
- Screenshots (all device sizes)
- Preview video (optional)
Testing
- TestFlight testing complete
- Crash-free rate acceptable
- Performance validated
Screenshot Sizes
| Device | Size |
|---|---|
| iPhone 6.7" | 1290 x 2796 |
| iPhone 6.5" | 1284 x 2778 |
| iPhone 5.5" | 1242 x 2208 |
| iPad Pro 12.9" | 2048 x 2732 |
Examples
/ios:publish --validate
/ios:publish --screenshots --metadata
/ios:publish --export
Output
# Publishing: [App Name]
## Validation: Pass/Fail
## Screenshots: Generated devices
## Metadata: Completeness status
## Next Steps: Submission actions
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.
- 4d ago First seen · 75 lines · 6 tokens per session scan A 971636c88622
publish is a command published in the GitHub repository CarolaneLFBV/ios-development-agents (7 stars, last pushed 1mo ago), licensed MIT. It adds 6 tokens to every session and 472 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
compose-test
Run Compose UI tests with Espresso. Verify critical user flows.
app-store-audit
Run an enterprise pre submission compliance audit on an iOS or Android app against Apple App Store and Google Play rejection rules. Pass a project path or run from the project root.
ios-privacy
Prepare privacy labels, permissions, policy links, and data-use truth for iOS release.
maestro-selectors-instructions
Guide to using Maestro selectors for targeting UI elements in tests.
initialize-ios
Manual override: initialize ast-index for iOS/Swift/ObjC project.
mobile-performance-check
Analyze mobile app for performance issues using the mobile-best-practices database.