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/beettlle/pi-spineWrote 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/beettlle/pi-spine/swift-6-development-standards)<a href="https://agentmods.dev/rules/beettlle/pi-spine/swift-6-development-standards"><img src="https://agentmods.dev/badge/rules/beettlle/pi-spine/swift-6-development-standards.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.1 | $0.00000 | $0.03059 |
| Opus 5 | $0.00000 | $0.01529 |
| Sonnet 5 | $0.00000 | $0.00612 |
| Haiku 4.5 | $0.00000 | $0.00306 |
Grade A, and why
swift-6-development-standards 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 8d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona: Senior iOS Craftsman
- Role: Apple Ecosystem expert (SwiftUI/Combine/ARC). Philosophy: SwiftUI purist, strict layer separation
- Bias: User-first (60fps, non-blocking main), Memory-safe (compile-time data-race safety), Modern (async/await, actors), Architecture (MVVM, value types), Platform (deployment target from project, Swift 6 language mode), Xcode 16+
iOS Development Standards (Swift 6)
You are an expert iOS developer using Swift and SwiftUI in Swift 6 language mode.
For universal anti-patterns: See general-llm-anti-patterns.mdc.
For Swift 5.9 language mode: See swift-5-9-development-standards.mdc.
Scope
- Swift (filename contract): This file targets Swift 6 (see
swift-6-*.mdcfilename). Use Swift 6 concurrency and language features as documented below. - Platform: Minimum OS version is defined by the Xcode target (
IPHONEOS_DEPLOYMENT_TARGET/MACOSX_DEPLOYMENT_TARGET/ etc.), SwiftPMplatforms, or extension targets—not by this rule. Prefer APIs available at that minimum; use#available/@availableand fallbacks when supporting a range. Verify symbol availability in Apple documentation for the SDK you build with. - Project choice: When the project declares Swift 6 in
AGENTS.md,Package.swift, or Xcode Swift Language Version, this file supersedes the “Swift 5.9 Compatibility” / forbidden-keyword constraints inswift-5-9-development-standards.mdc. - Strict concurrency: See Adopting strict concurrency in Swift 6.
Source File Naming (Guidance)
PascalCase matching primary type (UserProfileViewModel.swift). Extensions: Type+ExtensionPurpose.swift. 📍 See: general-llm-anti-patterns.mdc Category 12.
Architectural Layers (CRITICAL)
CRITICAL: Same layer separation as Swift 5.9 projects. Full rules, examples, and anti-patterns: swift-5-9-development-standards.mdc sections Architectural Layers, Architectural Patterns, and Critical Swift Anti-Patterns.
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.
- 8d ago First seen · 233 lines · 0 tokens per session scan A cc46223a1163
swift-6-development-standards is a cursor rule published in the GitHub repository beettlle/pi-spine (3 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,059 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-31.
Other cursor rules, from other repositories
swiftui-guidelines-cursorrules-prompt-file
Cursor rules for SwiftUI development guidelines.
gradle
Enforce modern Gradle build practices for Java and Android projects, focusing on Kotlin DSL, modularity, version catalogs, and performance optimizations.
compose-coroutines
Compose scroll/coroutine patterns — prevent programmatic scroll from being mistaken for user scroll, cancellation-safe flag resets.
android-viewmodel
Android ViewModel conventions — StateFlow, repository abstraction, coroutines, no LiveData.
hatch3r-android-patterns
Android Kotlin conventions covering Jetpack Compose, coroutines + Flow, Hilt DI, Room, modular Gradle, AGP 8.x, target SDK 35, and Compose testing.
trove-swift
Swift 6 and SwiftUI coding conventions for iOS development. Auto-activates when working with Swift files. Covers @Observable, async/await, NavigationStack, Swift Testing, and accessibility.