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 skills add FloWritesCode/fwc-swiftui-skills --skill swiftui-iphone-duogit clone --depth 1 https://github.com/FloWritesCode/fwc-swiftui-skillsWrote 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/skills/flowritescode/fwc-swiftui-skills/swiftui-iphone-duo)<a href="https://agentmods.dev/skills/flowritescode/fwc-swiftui-skills/swiftui-iphone-duo"><img src="https://agentmods.dev/badge/skills/flowritescode/fwc-swiftui-skills/swiftui-iphone-duo/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/flowritescode/fwc-swiftui-skills/swiftui-iphone-duo"><img src="https://agentmods.dev/badge/skills/flowritescode/fwc-swiftui-skills/swiftui-iphone-duo.svg" alt="Reviewed on agentmods" width="80" 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.00085 | $0.02566 |
| Opus 5 | $0.00043 | $0.01283 |
| Sonnet 5 | $0.00017 | $0.00513 |
| Haiku 4.5 | $0.00009 | $0.00257 |
Grade A, and why
swiftui-iphone-duo 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 4d 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SwiftUI iPhone Duo
Do not design a separate “Duo version” of the app.
Start with an adaptive SwiftUI interface that works across continuously changing widths and heights. Add Duo-specific behavior only when the fold, hinge, second display, or vertical system bars materially improve the experience.
The target is not “Make this app support iPhone Duo.” The target is:
Make this app excellent at every size, then use Duo's unique hardware where it creates additional value.
Before reviewing or changing layout, read the full rulebook: reference.md.
When to use
- User asks to support iPhone Duo, a foldable iPhone, hinge, fold, or two displays.
- User asks for adaptive SwiftUI layout across compact → wide, including multitasking.
- Code uses
UIDevice,UIScreen.main.bounds, idiom, orientation,isDuo, orisFoldedfor layout. - Work involves
ArrangementView, reserved regions,onHingeChange, or scene accessories.
Related skills
| Skill | When to load |
|---|---|
| swiftui-whats-new-27 | Toolbar overflow, visibilityPriority, ToolbarOverflowMenu, .topBarPinnedTrailing |
| swiftui-specialist | Broader SwiftUI layout and navigation correctness |
| swiftui-liquid-glass | System bars and glass chrome on iOS 26+ |
Optimization order
- Adaptive layout
- Adaptive navigation
- Adaptive toolbars and tabs
- Fold-safe positioning
- Duo-specific arrangements
- Hinge-driven interactions
- Second-display experiences
Progressive API tiers
Classify every change before writing code. Always complete Tier 1 before proposing Tier 2 or Tier 3.
Tier 1 — Universal adaptive improvements (do these first):
NavigationSplitView
adaptive TabView
adaptive grids
ViewThatFits
AnyLayout
size classes
container-relative sizing
system toolbars
safe-area correctness
These benefit all Apple platforms and window sizes.
Tier 2 — Duo-aware layout (only when needed):
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 269 lines · 85 tokens per session scan A 689224e5779f
swiftui-iphone-duo is a skill published in the GitHub repository FloWritesCode/fwc-swiftui-skills (255 stars, last pushed 5d ago), licensed MIT. It adds 85 tokens to every session and 2,566 once invoked, about $0.0004 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-11.
Other skills, from other repositories
animate-expo
Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and…
leanback-to-compose-tv-migration
Provides instructions and architectural patterns for migrating Android TV applications from legacy Leanback UI Toolkit, Android Views, or Support Fragments to Jetpack Compose for TV (androidx.tv). Use this skill for Leanback to Compose migrations, including browse screen, settings screen, authentication screen, login…
maui-data-binding
Guidance for .NET MAUI XAML and C# data bindings — compiled bindings, INotifyPropertyChanged / ObservableObject, value converters, binding modes, multi-binding, relative bindings, fallbacks, and MVVM best practices. USE FOR: setting up compiled bindings with x:DataType, implementing INotifyPropertyChanged or…
expo-brownfield
Framework (OSS). Integrate Expo and React Native into an existing native iOS or Android app. Use for brownfield, embedding a React Native screen in SwiftUI/UIKit or Kotlin, or AAR/XCFramework packaging. Covers isolated and integrated approaches. For building or distributing a purely native app with EAS, use…
migrate-xml-views-to-jetpack-compose
Provides a structured workflow for migrating an Android XML View to Jetpack Compose. This skill details the step-by-step process, from planning and dependency setup, to theming and layout migration, validation and XML cleanup. Use this skill when you need to migrate an XML View to Jetpack Compose in an Android…
web-haptics
Add haptic feedback to web apps using the web-haptics library. Use when building mobile-facing UIs that need tactile feedback on buttons, toggles, forms, pickers, and other interactive elements.