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/brunogama/ios-cursor-rulesWrote 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/rules/brunogama/ios-cursor-rules/create-ios-release)<a href="https://agentmods.dev/rules/brunogama/ios-cursor-rules/create-ios-release"><img src="https://agentmods.dev/badge/rules/brunogama/ios-cursor-rules/create-ios-release/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/rules/brunogama/ios-cursor-rules/create-ios-release"><img src="https://agentmods.dev/badge/rules/brunogama/ios-cursor-rules/create-ios-release.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.02440 |
| Opus 5.5 | $0.00000 | $0.00976 |
| Sonnet 5.5 | $0.00000 | $0.00488 |
| Haiku 4.5 | $0.00000 | $0.00244 |
Grade A, and why
create-ios-release 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 — 386 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS App Release Process
As an AI assistant helping with iOS app releases, I should guide through the following process for successfully deploying iOS applications to the App Store.
Versioning and Build Numbers
Version Numbering Scheme
- Follow semantic versioning (MAJOR.MINOR.PATCH):
- MAJOR: Breaking changes or significant UI redesigns
- MINOR: New features with backward compatibility
- PATCH: Bug fixes and minor improvements
- Update the version number in Xcode project settings (Info.plist)
- Increment build number for each submission, even for the same version
// Examining and updating Info.plist values programmatically
guard let infoPlistPath = Bundle.main.path(forResource: "Info", ofType: "plist"),
let infoPlist = NSDictionary(contentsOfFile: infoPlistPath) as? [String: Any] else {
return
}
let version = infoPlist["CFBundleShortVersionString"] as? String // Version number (e.g. "1.2.3")
let build = infoPlist["CFBundleVersion"] as? String // Build number (e.g. "42")
Git Tagging
- Tag each release in Git with the version number
- Use annotated tags with release notes
- Consider using a prefix like 'v' (e.g., v1.2.0)
# Create an annotated tag
git tag -a v1.2.0 -m "Version 1.2.0: Added dark mode support and fixed login issues"
# Push tags to remote
git push origin v1.2.0
Code Signing and Provisioning
Certificate Management
- Use Xcode's Automatic Code Signing when possible
- For manual signing, ensure certificates are properly installed and maintained
- Consider using cert/match tools from fastlane for team management
- Keep track of certificate expiration dates to avoid crisis
Provisioning Profiles
- Use appropriate profile types for different distribution methods:
- Development: For testing on developer devices
- Ad Hoc: For internal distribution to registered devices
- App Store: For App Store and TestFlight distribution
- Regenerate provisioning profiles when adding new devices or capabilities
- Keep profiles organized and up to date
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 · 386 lines · 0 tokens per session scan A 301ad881814d
create-ios-release is a cursor rule published in the GitHub repository brunogama/ios-cursor-rules (75 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,440 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 cursor rules, from other repositories
ipa-upload-automation
Universal IPA upload automation (TestFlight + optional App Store submission) for Flutter, React Native, and native Swift/Xcode projects.
swiftui
Rules for IcySky, a SwiftUI project for a bluesky client.
releasing
How to release AdLoop to PyPI — version bumping, tagging, and publishing.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.