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.
npx agentmods add rules/danielraffel/swiftcatalyst/swift-viper-architecturegit clone --depth 1 https://github.com/danielraffel/SwiftCatalystWrote 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/danielraffel/swiftcatalyst/swift-viper-architecture)<a href="https://agentmods.dev/rules/danielraffel/swiftcatalyst/swift-viper-architecture"><img src="https://agentmods.dev/badge/rules/danielraffel/swiftcatalyst/swift-viper-architecture.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.01570 | $0.01570 |
| Opus 5 | $0.00785 | $0.00785 |
| Sonnet 5 | $0.00314 | $0.00314 |
| Haiku 4.5 | $0.00157 | $0.00157 |
Grade A, and why
swift-viper-architecture 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@file ../Sources/Configuration/Configuration.swift @file ../Sources/Modules/Home/View/HomeView.swift
Swift VIPER Architecture Guidelines
General Guidelines
- Use the latest SwiftUI APIs and features whenever possible.
- Implement
async/awaitfor asynchronous operations. - Write clean, readable, and well-structured code.
- Follow the VIPER architecture to ensure modularity and scalability.
Project Structure
All code should follow the established project structure:
- Base directory: SwiftCatalyst
- Main code in: Sources
- VIPER modules in: Sources/Modules/[ModuleName]/[ComponentType]/[ModuleName][ComponentType].swift
File Naming Convention
- Module components should be named with the pattern [ModuleName][ComponentType].swift
- For example:
- HomeView.swift
- HomePresenter.swift
- HomeInteractor.swift
- HomeEntity.swift
- HomeRouter.swift
Project Configuration
Environment Variables
To make the project more configurable, use a .env file for environment-specific settings.
- Create a
.envfile in the project root (add it to your.gitignore) - Use the
.env.examplefile as a template for required variables - Run
./generate-project.shto create your project.yml from the template
The Configuration.swift file provides centralized access to all environment variables:
// Example usage:
let appName = Configuration.appName
let bundleId = Configuration.bundleIdPrefix + "." + Configuration.appName
This pattern allows for easy customization of:
- App name and bundle identifiers
- Team ID and app group ID
- API endpoints
- Feature flags
- Other environment-specific configuration
VIPER Architecture Overview
Each module in your SwiftUI app should follow the VIPER structure:
1. View
- The SwiftUI
Viewhandles user interface (UI) rendering and user interactions. - Import the
Injectframework to enable hot reloading. - Use
@ObserveInjectionto monitor changes for hot reloading. - Use the
.enableInjection()modifier in the view body.
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 · 225 lines · 1,570 tokens per session scan A 218717c8a225
swift-viper-architecture is a cursor rule published in the GitHub repository danielraffel/SwiftCatalyst (14 stars, last pushed 1y ago), licensed MIT. It adds 1,570 tokens to every session, about $0.0078 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-08-30.
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.
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.
android-viewmodel
Android ViewModel conventions — StateFlow, repository abstraction, coroutines, no LiveData.
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.