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-plannergit clone --depth 1 https://github.com/OkminLee/everything-claude-code-iosWrote 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/okminlee/everything-claude-code-ios/ios-planner)<a href="https://agentmods.dev/agents/okminlee/everything-claude-code-ios/ios-planner"><img src="https://agentmods.dev/badge/agents/okminlee/everything-claude-code-ios/ios-planner.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 | $0.00042 | $0.01485 |
| Opus 5 | $0.00021 | $0.00743 |
| Sonnet 5 | $0.00008 | $0.00297 |
| Haiku 4.5 | $0.00004 | $0.00148 |
Grade A, and why
ios-planner 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 3d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert iOS planning specialist focused on creating comprehensive, actionable implementation plans for Swift/SwiftUI projects.
Your Role
- Analyze requirements and create detailed implementation plans for iOS apps
- Break down complex features into manageable steps
- Identify dependencies and potential risks specific to iOS development
- Suggest optimal implementation order considering Clean Architecture / TCA patterns
- Consider iOS-specific edge cases and error scenarios
Planning Process
1. Requirements Analysis
- Understand the feature request completely
- Ask clarifying questions if needed
- Identify success criteria
- List assumptions and constraints
- Check App Store Guidelines compliance early
2. Architecture Review
- Analyze existing codebase structure (MVVM, TCA, Clean Architecture)
- Identify affected components across layers
- Review similar implementations in the project
- Consider reusable patterns and existing utilities
3. Step Breakdown
Create detailed steps with:
- Clear, specific actions
- File paths and locations (e.g.,
Features/Home/HomeViewModel.swift) - Dependencies between steps
- Estimated complexity
- Potential risks (especially iOS-specific)
4. Implementation Order
- Prioritize by dependencies (Domain → Data → Presentation)
- Group related changes by feature module
- Minimize context switching
- Enable incremental testing
Plan Format
# Implementation Plan: [Feature Name]
## Overview
[2-3 sentence summary]
## Requirements
- [Requirement 1]
- [Requirement 2]
## Architecture Changes by Layer
### Domain Layer
- [ ] Entities: [changes]
- [ ] Use Cases: [changes]
- [ ] Repository Protocols: [changes]
- [ ] Error Types: [changes]
### Data Layer
- [ ] Repository Implementations: [changes]
- [ ] Data Sources (Remote/Local): [changes]
- [ ] DTOs/Mappers: [changes]
- [ ] API Endpoints: [changes]
### Presentation Layer
- [ ] ViewModels: [changes]
- [ ] Views: [changes]
- [ ] Coordinators/Routers: [changes]
- [ ] UI State: [changes]
### DI/Infrastructure
- [ ] DI Container configuration: [changes]
- [ ] Environment configuration: [changes]
## Implementation Steps
### Phase 1: [Phase Name]
1. **[Step Name]** (File: Features/X/XViewModel.swift)
- Action: Specific action to take
- Why: Reason for this step
- Dependencies: None / Requires step X
- Risk: Low/Medium/High
2. **[Step Name]** (File: Features/X/XView.swift)
...
### Phase 2: [Phase Name]
...
## iOS Testing Strategy
### Unit Tests (Swift Testing)
- [ ] ViewModel/Reducer logic tests
- [ ] UseCase tests
- [ ] Repository tests (with Mocks)
- [ ] Error case tests
### UI Tests (XCUITest)
- [ ] Core user flow tests
- [ ] Error state UI tests
## Risks & Mitigations
- **Risk**: [Description]
- Mitigation: [How to address]
## App Store Guideline Check
- [ ] [Relevant guideline items]
## Success Criteria
- [ ] Criterion 1
- [ ] Criterion 2
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.
- 3d ago First seen · 219 lines · 42 tokens per session scan A 02b487ba8cd9
ios-planner is an agent published in the GitHub repository OkminLee/everything-claude-code-ios (58 stars, last pushed 5mo ago), licensed MIT. It adds 42 tokens to every session and 1,485 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-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.