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/moasq/ios-dev-agentWrote 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/moasq/ios-dev-agent/forbidden-patterns)<a href="https://agentmods.dev/rules/moasq/ios-dev-agent/forbidden-patterns"><img src="https://agentmods.dev/badge/rules/moasq/ios-dev-agent/forbidden-patterns/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/moasq/ios-dev-agent/forbidden-patterns"><img src="https://agentmods.dev/badge/rules/moasq/ios-dev-agent/forbidden-patterns.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.01452 | $0.01452 |
| Opus 5 | $0.00726 | $0.00726 |
| Sonnet 5 | $0.00290 | $0.00290 |
| Haiku 4.5 | $0.00145 | $0.00145 |
Grade A, and why
forbidden-patterns 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 5d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forbidden Patterns
Networking — Project-Scoped
Generated app code should be offline-first by default. Do not add arbitrary REST clients, analytics SDKs, or cloud calls unless the project explicitly requires and configures them. RevenueCat, StoreKit, WeatherKit, HealthKit, and Apple platform services are allowed when the relevant skill/configuration is in use.
UIKit — AVOID BY DEFAULT
Why: SwiftUI-first ensures cross-platform consistency.
- Prefer SwiftUI-first architecture
UIKitimports are allowed only when a required feature has no viable SwiftUI equivalentUIViewRepresentable/UIViewControllerRepresentableare allowed only as minimal bridges for those required UIKit features- No Storyboards, no XIBs, no Interface Builder
Third-Party Packages — SPM Only, Validated Before Use
Why: Dependencies add build complexity and supply chain risk. Use Apple frameworks first; add an SPM package only when it provides a meaningfully better experience.
Use SPM (Swift Package Manager) as the only package manager. CocoaPods and Carthage are not allowed.
When to add an SPM package
Add an SPM package when any of these apply:
- A feature needs capabilities that no Apple framework provides (e.g. playing After Effects / Lottie JSON animations, advanced image processing pipelines, barcode generation beyond Core Image).
- The approved-packages list below explicitly names a package for this project.
- The user's prompt explicitly requests a specific package by name.
Use native Apple frameworks when they cover the need well enough. For example, use Swift Charts instead of a charting library, use AsyncImage or PhotosUI instead of an image-loading library, and use Canvas / TimelineView for simple particle animations.
How to validate a package before adding it
Search the internet for the package. Then confirm each item:
- The GitHub repository exists and has more than 500 stars.
- The repository was updated within the last 12 months.
- The license is MIT or Apache 2.0.
- A
Package.swiftfile exists in the repository root (confirms SPM support). - Read the README to learn the correct import name and SwiftUI usage.
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.
- 5d ago First seen · 123 lines · 1,452 tokens per session scan A 04a1c7389816
forbidden-patterns is a cursor rule published in the GitHub repository moasq/ios-dev-agent (4 stars, last pushed 3mo ago), licensed MIT. It adds 1,452 tokens to every session, about $0.0073 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-09-03.
Other cursor rules, from other repositories
nativescript
NativeScript best practices and patterns for mobile applications.
performance-optimization
// Use weak/unowned references appropriately class ViewController: UIViewController { private var timer: Timer?
webkit-browser
Cursor rule "webkit-browser" from duckduckgo/apple-browsers, covering webkit & browser development guidelines, webview configuration, basic webview setup, user scripts management and tab management.
maestro-device-selection
Maestro tests can run on either iPhone or iPad simulators based on tags in the test YAML files. This allows you to test iPad-specific UI layouts and features while maintaining a single test suite.
cursorrules
Kortix is a React Native + Expo app built with TypeScript, NativeWind (Tailwind CSS), and a custom design system.
gradle
Enforce modern Gradle build practices for Java and Android projects, focusing on Kotlin DSL, modularity, version catalogs, and performance optimizations.