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/bravew/trove/trove-swiftgit clone --depth 1 https://github.com/bravew/troveWrote 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/bravew/trove/trove-swift)<a href="https://agentmods.dev/rules/bravew/trove/trove-swift"><img src="https://agentmods.dev/badge/rules/bravew/trove/trove-swift.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 | $0.00000 | $0.00489 |
| Opus 5 | $0.00000 | $0.00244 |
| Sonnet 5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
trove-swift 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 4d 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.
What it actually says
Trove · v2026.7.4
Session Init
This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.
Swift 6 / SwiftUI Conventions
@Observable (Preferred over ObservableObject)
@Observable
final class UserViewModel {
var name = ""
var isLoading = false
func load() async {
isLoading = true
defer { isLoading = false }
name = try await fetchUserName()
}
}
Use @Observable instead of ObservableObject + @Published in new code.
Async/Await
- Use structured concurrency (
async let,TaskGroup) - Annotate main-actor-bound code with
@MainActor - Use
Task { }only at boundaries (view lifecycle, button actions)
// Parallel fetching
async let user = fetchUser(id)
async let posts = fetchPosts(userId: id)
let (userData, postsData) = try await (user, posts)
NavigationStack
NavigationStack(path: $router.path) {
ContentView()
.navigationDestination(for: Route.self) { route in
switch route {
case .detail(let id): DetailView(id: id)
case .settings: SettingsView()
}
}
}
Error Handling
- Use typed
throwswhere possible - Define domain-specific error enums conforming to
LocalizedError - Never force-unwrap (
!) outside of tests
AI Gotchas
- Sendable: Mark types shared across concurrency domains as
Sendable - MainActor: UI updates must happen on
@MainActor - Observation:
@ObservablereplacesObservableObjectin Swift 5.9+ - SwiftUI previews: Use
#Previewmacro instead ofPreviewProvider
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.
- 4d ago First seen · 74 lines · 489 tokens per session scan A e5d3dfca659e
trove-swift is a cursor rule published in the GitHub repository bravew/trove (10 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 489 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
data-rules
Cursor rule "data-rules" from HeeGyeong/ComposeSample, covering data class implementation rules, key rules, naming conventions, required structure and mandatory annotations.
android-viewmodel
Android ViewModel conventions — StateFlow, repository abstraction, coroutines, no LiveData.
cursorrules
ROLE: Android Development Expert EXPERIENCELEVEL: Advanced (10+ years) SPECIALTIES.
swift-observable
Migration guide for updating SwiftUI apps from ObservableObject to the @Observable macro.
modern-swift
Write idiomatic SwiftUI code following Apple's latest architectural recommendations and best practices.
xcf-quickref
Cursor rule "xcf-quickref" from CodeFreezeAI/xcf, covering xcf quick reference guide 🚀, 🎛️ xcf core actions, permissions & project management, build & execute and system & analysis.