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/with-ios)<a href="https://agentmods.dev/rules/brunogama/ios-cursor-rules/with-ios"><img src="https://agentmods.dev/badge/rules/brunogama/ios-cursor-rules/with-ios/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/with-ios"><img src="https://agentmods.dev/badge/rules/brunogama/ios-cursor-rules/with-ios.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.02404 |
| Opus 5.5 | $0.00000 | $0.00962 |
| Sonnet 5.5 | $0.00000 | $0.00481 |
| Haiku 4.5 | $0.00000 | $0.00240 |
Grade A, and why
with-ios 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 2mo 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 — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS Development Best Practices
As an AI assistant working on iOS applications, I should follow these guidelines to ensure high-quality, user-friendly, and efficient iOS apps.
iOS App Architecture
Architecture Patterns
-
Use appropriate architecture patterns based on app complexity:
- MVC: Simple apps or when following Apple's basic patterns
- MVVM: Medium complexity apps, works well with SwiftUI/Combine
- VIPER/Clean: Complex apps requiring clear separation of concerns
- Composable Architecture: Advanced reactive apps with predictable state management
-
Keep view controllers/views lightweight by moving business logic to separate components
-
Use coordinator pattern for complex navigation flows
-
Consider feature-based modularization for large applications
Project Organization
- Organize project by feature, not by type
- Use Swift packages to modularize components
- Group related files in logical folders
- Utilize Xcode's project navigator groups to maintain code organization
AppProject/
├── Core/
│ ├── Networking/
│ ├── Storage/
│ ├── Authentication/
│ └── Common UI Components/
├── Features/
│ ├── User Profile/
│ │ ├── Models/
│ │ ├── Views/
│ │ └── ViewModels/
│ ├── Shopping Cart/
│ │ ├── Models/
│ │ ├── Views/
│ │ └── ViewModels/
├── Resources/
│ ├── Assets.xcassets/
│ ├── Localization/
│ └── Fonts/
└── Supporting Files/
├── AppDelegate.swift
├── SceneDelegate.swift
├── Info.plist
└── Configuration/
UIKit vs SwiftUI
When to Use UIKit
- When targeting iOS 12 or earlier
- For complex custom UI that's difficult to implement in SwiftUI
- When you need precise control over UI performance optimization
- For apps heavily dependent on UIKit-specific features
When to Use SwiftUI
- For new apps targeting iOS 14+
- For rapid development and prototyping
- When you want to share UI code across Apple platforms
- For list-based interfaces and standard UI components
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.
- 2mo ago First seen · 358 lines · 0 tokens per session scan A 2872d22d8349
with-ios 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,404 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
swiftui
Rules for IcySky, a SwiftUI project for a bluesky client.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.