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 skills add dagba/ios-mcp --skill realm-persistencegit clone --depth 1 https://github.com/dagba/ios-mcpWrote 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/skills/dagba/ios-mcp/realm-persistence)<a href="https://agentmods.dev/skills/dagba/ios-mcp/realm-persistence"><img src="https://agentmods.dev/badge/skills/dagba/ios-mcp/realm-persistence.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.00037 | $0.02899 |
| Opus 5 | $0.00018 | $0.01450 |
| Sonnet 5 | $0.00007 | $0.00580 |
| Haiku 4.5 | $0.00004 | $0.00290 |
Grade A, and why
realm-persistence 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 7d 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 — 428 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Realm Persistence for iOS
Overview
Realm's thread-confinement model conflicts with Swift Concurrency's thread-hopping. The zero-copy architecture delivers fast reads but causes memory traps in extensions. Wrong patterns cause "accessed from incorrect thread" crashes.
Core principle: Fresh Realm per actor method, batch all writes, never pass objects across threads, avoid Realm in memory-constrained contexts.
Threading Model
Critical Rule: Thread-Confined Objects
Realm objects CAN ONLY be accessed on the thread where Realm was created.
digraph threading {
"Using async/await?" [shape=diamond];
"Memory-constrained? (widget, extension)" [shape=diamond];
"Use actor + fresh Realm()" [shape=box, style=filled, fillcolor=lightgreen];
"Use @MainActor + stored Realm" [shape=box, style=filled, fillcolor=lightblue];
"Don't use Realm" [shape=box, style=filled, fillcolor=red];
"Using async/await?" -> "Memory-constrained? (widget, extension)" [label="yes"];
"Using async/await?" -> "Use @MainActor + stored Realm" [label="no"];
"Memory-constrained? (widget, extension)" -> "Don't use Realm" [label="yes"];
"Memory-constrained? (widget, extension)" -> "Use actor + fresh Realm()" [label="no"];
}
Pattern 1: Actor + Fresh Realm (Async/Await)
CRITICAL: With async/await, tasks can resume on ANY thread. Stored Realm instance = crash.
// ❌ WRONG: Stored Realm with async
class TaskManager {
let realm: Realm // Created on Thread A
async func fetchTasks() -> [Task] {
// May execute on Thread B after suspension
return Array(realm.objects(Task.self)) // CRASH: incorrect thread
}
}
// ✅ CORRECT: Fresh Realm per method
actor TaskManager {
func fetchTasks() async throws -> [Task] {
let realm = try Realm() // New Realm on actor's thread
return Array(realm.objects(Task.self))
}
func updateTask(_ id: String, completed: Bool) async throws {
let realm = try Realm() // Fresh instance, same actor thread
guard let task = realm.object(ofType: Task.self, forPrimaryKey: id) else {
return
}
try realm.write {
task.isCompleted = completed
}
}
}
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.
- 7d ago First seen · 428 lines · 37 tokens per session scan A db494c376f3c
realm-persistence is a skill published in the GitHub repository dagba/ios-mcp (3 stars, last pushed 7mo ago), licensed MIT. It adds 37 tokens to every session and 2,899 once invoked, about $0.0002 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-31.
Other skills, from other repositories
setup-datamodel
Use when the user wants to design or redesign the Dataverse schema and connector plan for an existing mobile app, or has an ER diagram (image, Mermaid, or text) to apply. Skip when the user is creating a brand-new app — /create-mobile-app handles the data model inline.
axiom-audit-swiftdata
Use when the user mentions SwiftData review, @Model issues, SwiftData migration safety, or SwiftData performance checking.
axiom-audit-core-data
Use when the user mentions Core Data review, schema migration, production crashes, or data safety checking.
firebase-database
Use when syncing real-time data, structuring JSON trees, reading/writing, creating listeners, enabling offline persistence, managing presence, sharding, or writing security rules.
axiom-data
Use when working with ANY data persistence, database, storage, CloudKit, migration, or serialization. Covers SwiftData, Core Data, GRDB, SQLite, Realm, CloudKit sync, file storage, Codable, migrations.
android-data-layer
Guidance on implementing the Data Layer using Repository pattern, Room (Local), and Retrofit (Remote) with offline-first synchronization.