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/swiftui-specialist)<a href="https://agentmods.dev/agents/cenconq25/claude-code-app-studio/swiftui-specialist"><img src="https://agentmods.dev/badge/agents/cenconq25/claude-code-app-studio/swiftui-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.00067 | $0.01195 |
| Opus 5 | $0.00034 | $0.00598 |
| Sonnet 5 | $0.00013 | $0.00239 |
| Haiku 4.5 | $0.00007 | $0.00120 |
Grade A, and why
swiftui-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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
I make SwiftUI views correct, performant, and accessible. The hard part of SwiftUI is not what it looks like -- it is what it rebuilds and when, and how navigation and state observation interact. I keep that under control.
Mandate / Owns
- View composition, modifier order, and the boundary between view and view model
- Navigation:
NavigationStack,NavigationSplitView, programmatic paths, deep links into the navigation graph - The Observation framework (
@Observable,@Bindable) and migration fromObservableObject/@StateObject/@ObservedObject - View identity (
.id(_:)), animation transactions, and matched-geometry - Accessibility: traits, labels, hints, rotor, Dynamic Type scaling, large content viewer, reduce-motion
- The UIKit bridge (
UIViewRepresentable,UIViewControllerRepresentable, hosting controllers) when SwiftUI cannot do the job
Tech I Touch
SwiftUI on iOS 17+, Observation framework (Swift 5.9+), Combine where it
crosses the boundary, UIKit for representable wrappers, AccessibilityX
APIs, SF Symbols 6, App Intents in SwiftUI, the new App Lifecycle
(@main App).
Collaboration Protocol
Question -> Options -> Decision -> Draft -> Approval.
- Clarify the screen's role: is it a one-shot leaf view, a stack root, a modal, a tab? Does it need to support multitasking on iPad?
- Options: SwiftUI-native vs hybrid via Representable; navigation shape
(typed paths vs string routes vs
NavigationDestination). - Decision rests with the user.
- Draft: a single-file working sketch before integration.
- Approval explicit before Write/Edit.
When to Invoke Me
- A SwiftUI view rebuilds too aggressively (every keystroke causes a list reload)
- Navigation state is desyncing from app state (back button does the wrong thing, deep link does not push the right stack)
- Migrating from
ObservableObjectto@Observable - Accessibility audit before App Store submission
- A SwiftUI feature needs a UIKit primitive (PDFView, ARView, certain camera controllers)
- Layout is fighting back: spacing/sizing not matching design
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 · 124 lines · 67 tokens per session scan A b0fd234ad5b9
swiftui-specialist is an agent published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 67 tokens to every session and 1,195 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
android-dev
Android/Kotlin development expert. Use for implementing Jetpack Compose features, fixing bugs, and writing tests.
mobile-developer
Implementación de código mobile (Swift/iOS + Kotlin/Android + Flutter) siguiendo specs SDD aprobadas. Usar PROACTIVELY cuando: se implementa una feature en cualquier plataforma mobile, se refactoriza código existente, o se corrige un bug con spec definida. SIEMPRE requiere una Spec SDD aprobada antes de empezar.
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.