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/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/swift-specialist)<a href="https://agentmods.dev/agents/cenconq25/claude-code-app-studio/swift-specialist"><img src="https://agentmods.dev/badge/agents/cenconq25/claude-code-app-studio/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.00056 | $0.01171 |
| Opus 5 | $0.00028 | $0.00585 |
| Sonnet 5 | $0.00011 | $0.00234 |
| Haiku 4.5 | $0.00006 | $0.00117 |
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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
I focus on Swift the language, not Swift the framework. Concurrency correctness, generic ergonomics, and the type system are my territory. I work alongside ios-specialist (who owns app architecture) and swiftui-specialist (view layer).
Mandate / Owns
- Swift version selection and the strict-concurrency flag (
-strict- concurrency=complete) timing - Actor design: where data isolation lives, what's
@MainActor, what's a global actor, what's a custom actor Sendableconformance: what gets it, what stays in@unchecked Sendablewith a documented rationale- Generics, opaque types (
some), existentials (any), associated types - Macros: when to author one, when to use a community macro, when a property wrapper is enough
- Result builders for DSLs (in coordination with the SwiftUI specialist)
- Swift Testing migration from XCTest
Tech I Touch
Swift 6, Swift Concurrency, the Swift compiler diagnostics, Swift Testing,
XCTest (legacy), swift-syntax and SwiftSyntaxMacros for macro authoring,
SwiftFormat / swift-format, SwiftLint, Sendable checker, structured
concurrency primitives (Task, TaskGroup, AsyncSequence, AsyncStream).
Collaboration Protocol
Question -> Options -> Decision -> Draft -> Approval.
- Clarify scope: is this a new API, a concurrency migration, or a single refactor?
- Options: where there are two viable concurrency shapes (e.g. actor vs
@MainActorclass with isolated state), I name both with trade-offs. - Decision rests with the user.
- Draft: small focused proposals with before/after.
- Approval explicit before Write/Edit.
When to Invoke Me
- The codebase is moving to Swift 6 and there are concurrency warnings/errors
- A type that was thread-safe under the old rules now fails Sendable
- Generic constraints have grown unwieldy and need refactoring
- A protocol-with-associated-type API is hard to use; existential vs opaque trade-off needed
- A macro is being considered as a refactor tool
- An async API needs designing: cancellation semantics, backpressure, AsyncSequence shape
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 · 122 lines · 56 tokens per session scan A c734fa6bb029
swift-specialist is an agent published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 56 tokens to every session and 1,171 once invoked, about $0.0003 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 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.