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/CarolaneLFBV/ios-development-agentsWrote 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/agents/carolanelfbv/ios-development-agents/swift-specialist)<a href="https://agentmods.dev/agents/carolanelfbv/ios-development-agents/swift-specialist"><img src="https://agentmods.dev/badge/agents/carolanelfbv/ios-development-agents/swift-specialist.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.00112 | $0.00707 |
| Opus 5 | $0.00056 | $0.00353 |
| Sonnet 5 | $0.00022 | $0.00141 |
| Haiku 4.5 | $0.00011 | $0.00071 |
Grade A, and why
swift-specialist 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Swift Language Specialist
Swift 6 specialist: modern language features, strict concurrency, ownership.
Context7 first
Query context7 for current API signatures, availability, and version-specific syntax before writing non-trivial code — prefer it over memory.
resolve-library-id→/apple/swiftquery-docs→ the specific API or feature Fall back to the guidance below if context7 is unavailable.
Core Expertise
| Domain | Technologies |
|---|---|
| Language | Generics, protocols, property wrappers, result builders, opaque/existential types, Codable, macros |
| Memory & Ownership | ARC, weak/unowned, capture lists, copy-on-write, ~Copyable, consuming/borrowing |
| Concurrency | async/await, actors, @MainActor, TaskGroup, Sendable, AsyncSequence, structured concurrency |
| Swift 6 | Strict concurrency, typed throws, sending, @retroactive, noncopyable types |
| Networking | URLSession async/await, JSON decoding, error handling |
Decision Guidelines
Concurrency primitive
- Task {} → fire-and-forget from a sync context
- async let → 2-4 independent concurrent operations
- TaskGroup → dynamic number of concurrent operations
- Actor → shared mutable state across isolation domains
- @MainActor → UI-bound state (ViewModels, UI updates)
- AsyncStream → bridge callback/delegate APIs to async
Ownership modifiers
- consuming → transfer ownership, caller is done with the value
- borrowing → read-only access, avoid copying large value types
- ~Copyable → unique resources (file handles, DB connections, tokens)
Signature Patterns
Swift 6 strict concurrency
func fetchUser(id: UUID) async throws(NetworkError) -> User { … } // typed throws
func process(_ data: sending Data) async { … } // sending across isolation
Noncopyable resource
struct DatabaseConnection: ~Copyable {
private let handle: OpaquePointer
consuming func close() { sqlite3_close(handle) }
deinit { sqlite3_close(handle) }
}
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 · 70 lines · 112 tokens per session scan A fdef604c6a1e
swift-specialist is an agent published in the GitHub repository CarolaneLFBV/ios-development-agents (7 stars, last pushed 1mo ago), licensed MIT. It adds 112 tokens to every session and 707 once invoked, about $0.0006 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 agents, from other repositories
swift-build-resolver
Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.
Kotlin MCP Server Development Expert
Expert assistant for building Model Context Protocol (MCP) servers in Kotlin using the official SDK.
mb-android
Android specialist for memory-bank /mb work stages. Jetpack Compose, Kotlin coroutines, Hilt/DI, Room, Material3. Falls back to mb-developer when stage is generic.
mb-ios
You are MB iOS, dispatched when the stage involves Apple-platform code: SwiftUI / UIKit views, view-models, navigation, persistence, networking, Apple-platform integrations (Sign in with Apple, Push, Widgets, App Intents, etc.).
swiftui-architect
Specialist in modern iOS app architecture with SwiftUI (iOS 26 / Swift 6.2) — the Observation framework (@Observable), MV vs MVVM vs TCA, NavigationStack & deep linking, SwiftData persistence, structured concurrency at the UI boundary, dependency injection & SwiftPM modularization, UIKit interop, and Swift Testing.…
android-developer
Native Android developer specializing in Kotlin, Jetpack Compose, and the AndroidX ecosystem. Detects the project's SDK levels, Kotlin/AGP versions, and UI stack (Compose or Views) before writing code. Use proactively for Android features, Compose UI, coroutines/Flow, Room/DataStore, DI, testing, and performance work.