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/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/native-ios)<a href="https://agentmods.dev/rules/kensaurus/cursor-kenji/native-ios"><img src="https://agentmods.dev/badge/rules/kensaurus/cursor-kenji/native-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/kensaurus/cursor-kenji/native-ios"><img src="https://agentmods.dev/badge/rules/kensaurus/cursor-kenji/native-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.00588 |
| Opus 5.5 | $0.00000 | $0.00235 |
| Sonnet 5.5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
native-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 26d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Native iOS
The developer has no Mac: iOS code is written here and verified on CI,
so local Xcode, pod install, and xcodebuild are not options to
suggest.
Adjust
ios/to your repo's actual path (e.g.apps/mobile/ios/).
Stack: Swift first, Obj-C only for RN bridge boilerplate.
Build: Xcode + CocoaPods on the CI runner.
Deployment target: read ios/Podfile platform :ios, 'X.Y'; raise it
only after checking which RN libraries it breaks.
Conventions
- Native modules for RN:
*.swiftfor logic +*.mbridge withRCT_EXTERN_METHODdeclarations. - Async: Swift Concurrency (
async/await,Task). Combine only where the API requires it. - No callback pyramids. No
DispatchQueue.main.asyncwrapping unless updating UIKit on a background queue. - Logging:
os_logorLoggerwith subsystem matching the bundle ID. - UI: SwiftUI for new screens; programmatic UIKit if existing patterns require it.
- Strings:
Localizable.strings. No hardcoded user-facing text. - Permissions: usage descriptions in
Info.plist(NSCameraUsageDescription, NSMicrophoneUsageDescription, etc.) AND runtime requests.
Verification (CI only)
After editing iOS files:
- Make the edit.
- Suggest
/rn-verifyto catch JS/Android-side issues. - When ready, suggest
/rn-ship-iosto push and trigger CI. - If CI fails, use
/ios-ci-logsto diagnose.
Special case: if the change is purely in Info.plist strings
(e.g., adding a permission description), it's worth flagging that
the change is low-risk but must still go through CI.
Boundaries
- Do not edit
*.pbxprojby hand. The developer can't open Xcode to fix a corrupted project file. - Do not bump
Podfile.lockunless that's the explicit task —pod installruns on CI. - Do not change
IPHONEOS_DEPLOYMENT_TARGETwithout checking which RN libs it breaks. - Do not commit
.xcuserstate,xcuserdata/, orios/build/. - Do not claim iOS changes are verified just because TS passed — the developer must trigger CI.
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.
- 26d ago Changed · -3 lines fe38166f3e21
- 1mo ago First seen · 65 lines · 0 tokens per session scan A d9b48f6c9add
native-ios is a cursor rule published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 588 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-09-03.
Other cursor rules, from other repositories
kotlin-rules
You are a Senior Kotlin programmer with experience in the Android framework and a preference for clean programming and design patterns.
flutter-rules
You are an expert in Flutter, Dart, Riverpod, Freezed, Flutter Hooks, and Supabase.
04-kotlin
Cursor rule "04-kotlin" from orbitalsonic/AndroidPilot, covering kotlin rules, prefer, coroutines, null safety and naming.
swift-uikit-cursorrules-prompt-file
Cursor rules for Swift Uikit.
swiftui-guidelines-cursorrules-prompt-file
Cursor rules for SwiftUI development guidelines.
android-jetpack-compose-cursorrules-prompt-file
Cursor rules for Android development with Jetpack Compose integration.