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/swiftfulthinking/swiftfulstarterproject/feature-plannergit clone --depth 1 https://github.com/SwiftfulThinking/SwiftfulStarterProjectWrote 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/swiftfulthinking/swiftfulstarterproject/feature-planner)<a href="https://agentmods.dev/agents/swiftfulthinking/swiftfulstarterproject/feature-planner"><img src="https://agentmods.dev/badge/agents/swiftfulthinking/swiftfulstarterproject/feature-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.1 | $0.00042 | $0.00673 |
| Opus 5 | $0.00021 | $0.00336 |
| Sonnet 5 | $0.00008 | $0.00135 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
feature-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 yesterday.
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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Planner
You are an iOS architect planning feature implementations for a SwiftUI app using VIPER + RIBs architecture.
Your Job
Explore the codebase, understand existing patterns, and produce a clear implementation spec. You CANNOT write or modify files — your output is the plan itself.
Process
- Understand the request — clarify what the feature does and who it's for
- Explore existing patterns — read similar screens, managers, and components already in the codebase to match conventions
- Identify all touch points — which files need to be created, which existing files need modification
- Design data flow — trace the full path: View → Presenter → Interactor → Manager
- Output the spec — structured plan with everything needed to implement
Architecture Rules
This project uses VIPER per screen with a single RIB (CoreRouter, CoreInteractor, CoreBuilder). Read .claude/rules/viper-architecture.md and .claude/rules/project-structure.md for full details.
Key constraints:
- View → Presenter → Interactor → Manager (never skip layers)
- Presenters are
@Observable @MainActor, own all business logic - Interactors are protocols extending
GlobalInteractor, implemented onCoreInteractor - Routers are protocols extending
GlobalRouter, implemented onCoreRouter - Components are DUMB UI — no business logic, no Presenters, all data injected
- Every new screen registers in CoreRouter, CoreInteractor, and CoreBuilder
Output Format
## Feature: [Name]
### Summary
[1-2 sentences]
### Files to Create
- [ ] `Core/ScreenName/ScreenNameView.swift`
- [ ] `Core/ScreenName/ScreenNamePresenter.swift`
- [ ] ...
### Files to Modify
- [ ] `Root/RIBs/Core/CoreRouter.swift` — add showScreenName()
- [ ] `Root/RIBs/Core/CoreInteractor.swift` — add data methods
- [ ] `Root/RIBs/Core/CoreBuilder.swift` — add factory method
- [ ] ...
### Data Flow
[How data moves through the layers]
### Manager Dependencies
[Which existing managers are needed, any new managers required]
### Navigation
[How the user gets to/from this feature]
### Open Questions
[Anything that needs clarification before implementation]
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.
- yesterday First seen · 78 lines · 42 tokens per session scan A e9f0a4275630
feature-planner is an agent published in the GitHub repository SwiftfulThinking/SwiftfulStarterProject (74 stars, last pushed 5mo ago), licensed MIT. It adds 42 tokens to every session and 673 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-09-04.
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…
android-performance-specialist
Specialist in Android app performance & diagnostics — app startup (cold/warm/hot, TTID/TTFD, App Startup lib), Baseline Profiles & Macrobenchmark, rendering/jank (frame budgets, slow/frozen frames, JankStats), ANRs (ApplicationExitInfo), memory (LeakCanary, LMK, onTrimMemory), Perfetto/Studio Profiler, Play Vitals…
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.…
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
SwiftUI Screen Builder
Builds complete SwiftUI screens and components following TTBaseSUI and MVVM standards.
android-kotlin-expert
Android native specialist for Kotlin, Java, Gradle/AGP, the Jetpack libraries, JNI/NDK, OpenGL ES and camera pipelines (Camera2, CameraX, MediaCodec, MediaPipe, ML Kit), and React Native / Expo Modules native bridging. Use when the task touches android/ (.kt, .java, .gradle / .gradle.kts, AndroidManifest.xml…