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 agents/okminlee/everything-claude-code-ios/ios-architect-examplegit clone --depth 1 https://github.com/OkminLee/everything-claude-code-iosWhat 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.01114 |
| Opus 5 | $0.00000 | $0.00557 |
| Sonnet 5 | $0.00000 | $0.00223 |
| Haiku 4.5 | $0.00000 | $0.00111 |
Grade A, and why
ios-architect-example 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 2d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ios-architect 사용 예제
새 프로젝트 아키텍처 설계 세션 예시입니다.
시나리오
신규 iOS 앱 프로젝트의 아키텍처를 설계하는 상황입니다.
세션 예시
사용자 요청
@ios-architect
새로운 이커머스 앱을 개발하려고 합니다.
- iOS 17+ 타겟
- 2-3명 규모 팀
- 오프라인 지원 필요
- 결제 기능 포함
아키텍처를 설계해주세요.
에이전트 응답 예시
## 1. 아키텍처 분석
### 요구사항 정리
- **팀 규모**: 2-3명 (중소규모)
- **iOS 버전**: 17+ (최신 API 활용 가능)
- **핵심 기능**: 오프라인 지원, 결제
### 권장 아키텍처: Clean Architecture + MVVM
팀 규모와 프로젝트 복잡도를 고려할 때, TCA보다 MVVM이 적합합니다.
- TCA는 학습 곡선이 높고 보일러플레이트가 많음
- MVVM은 팀원들이 쉽게 적응 가능
## 2. 프로젝트 구조
EcommerceApp/ ├── App/ │ ├── EcommerceApp.swift # @main │ └── AppDelegate.swift ├── Core/ │ ├── DI/ │ │ └── Container.swift # 의존성 컨테이너 │ ├── Extensions/ │ └── Utilities/ ├── Domain/ │ ├── Entities/ │ │ ├── Product.swift │ │ ├── Cart.swift │ │ └── Order.swift │ ├── UseCases/ │ │ ├── ProductUseCase.swift │ │ └── OrderUseCase.swift │ └── Repositories/ # 프로토콜만 │ ├── ProductRepositoryProtocol.swift │ └── OrderRepositoryProtocol.swift ├── Data/ │ ├── Repositories/ # 구현체 │ │ ├── ProductRepository.swift │ │ └── OrderRepository.swift │ ├── Network/ │ │ ├── APIClient.swift │ │ └── Endpoints/ │ ├── Persistence/ │ │ ├── SwiftDataContainer.swift │ │ └── Models/ │ └── Mappers/ ├── Features/ │ ├── Home/ │ │ ├── HomeView.swift │ │ └── HomeViewModel.swift │ ├── ProductDetail/ │ ├── Cart/ │ ├── Checkout/ │ └── Profile/ └── Resources/
## 3. 핵심 설계 결정
### 오프라인 지원
- **SwiftData** 사용 (iOS 17+ 전용)
- Repository 패턴으로 로컬/원격 데이터 소스 추상화
- 동기화 전략: 온라인 복귀 시 자동 동기화
### 결제
- **StoreKit 2** 사용
- 서버 사이드 영수증 검증 필수
- 별도 PaymentService로 분리
### 상태 관리
- **@Observable** 사용 (iOS 17+)
- @ObservableObject 대비 보일러플레이트 감소
- fine-grained 업데이트로 성능 향상
## 4. 의존성
```swift
// Package.swift
dependencies: [
// 네트워크
.package(url: "https://github.com/Alamofire/Alamofire.git", from: "5.8.0"),
// 이미지
.package(url: "https://github.com/onevcat/Kingfisher.git", from: "7.10.0"),
// 린팅
.package(url: "https://github.com/nicklockwood/SwiftFormat.git", from: "0.53.0"),
]
5. 다음 단계
- 프로젝트 생성 및 폴더 구조 설정
- Core/DI 컨테이너 구현
- Domain 레이어 Entity 정의
- Data 레이어 Repository 구현
- 첫 번째 Feature (Home) TDD로 개발
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.
- 2d ago First seen · 141 lines · 0 tokens per session scan A 9ad07675b535
ios-architect-example is an agent published in the GitHub repository OkminLee/everything-claude-code-ios (58 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,114 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-30.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
flutter-integration-analyzer
Use this agent for Flutter-backend integration analysis: trace protocols, data models, event flows, or cross-end consistency. Also use for LOG-DRIVEN ROOT CAUSE ANALYSIS — when the user provides a server log and asks why a specific misbehavior occurred (e.g. "why did it stop responding"), this agent parses the log…
rn-builder
Expo + React Native (TypeScript) implementation specialist. Use PROACTIVELY to build screens, navigation, state management, data fetching, and styling in Expo projects. Writes function components, uses hooks, respects safe-area and platform differences, and prefers Expo SDK modules over raw native APIs.
mobile-specialist
モバイルUI・プラットフォームガイドラインの専門家。 iOS HIG / Material Design準拠、レスポンシブ対応、プラットフォーム固有パターンを評価する。 ui-review チームの一員として起動される。.
copilot
cd your-android-project git clone https://github.com/haidrrrry/compose-kotlin-agent-skills.git .github/skills/compose-kotlin-agent-skills.