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 skills/martinpuli/createanapp/ios-app-buildernpx skills add MartinPuli/createAnApp --skill ios-app-buildergit clone --depth 1 https://github.com/MartinPuli/createAnAppWrote 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/martinpuli/createanapp/ios-app-builder)<a href="https://agentmods.dev/skills/martinpuli/createanapp/ios-app-builder"><img src="https://agentmods.dev/badge/skills/martinpuli/createanapp/ios-app-builder.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.00069 | $0.00668 |
| Opus 5 | $0.00034 | $0.00334 |
| Sonnet 5 | $0.00014 | $0.00134 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
ios-app-builder 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 5d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS App Builder
Implement in vertical slices against acceptance criteria. Do not present prototype controls, mock exports, placeholder data, or unverified commerce as finished functionality.
Establish a trustworthy baseline
- Inspect repository instructions and dirty state.
- Build and test before editing.
- Record workspace/project, scheme, bundle, device families, deployment target, versions, signing mode, dependencies, entitlements, manifest, and existing failures.
- Map every public/product promise to current source and tests.
- Use
$apple-agent-toolchainif the build environment is not verified.
Implement vertical slices
For each slice:
- model and validation;
- persistence/migration;
- service or platform boundary;
- adaptive UI and all states;
- accessibility identifiers and semantics;
- unit/integration/UI tests;
- error, cancellation, offline, and recovery behavior;
- documentation and acceptance evidence.
Prefer native frameworks and a minimal dependency set. Keep secrets server-side or in protected configuration. Never embed private API keys in the app.
Persistence and migrations
Use atomic writes or a transactional store. Test exact round trips, corruption/error handling, app termination/relaunch, upgrades from prior schema, deletion/export, backup behavior, and storage-pressure failure. State where data lives and what deleting the app does.
StoreKit 2
Use stable product identifiers that match App Store Connect. Implement product loading, localized Apple pricing, purchase verification, current entitlement reconstruction at launch, transaction updates, restore/sync, expiration, refund/revocation, pending/cancelled/failure states, billing retry/grace behavior if applicable, offline caching without false access, and accessible legal/paywall surfaces.
Maintain a checked-in StoreKit configuration with fake local transactions only; never treat it as Sandbox/TestFlight proof.
Privacy and platform integration
- Request permissions in context and explain denied recovery.
- Maintain
PrivacyInfo.xcprivacyand required-reason API declarations. - Inventory network endpoints, SDKs, entitlements, background modes, URL schemes, and data flows.
- Keep support, privacy, and Terms links reachable.
- Ensure features function on every declared device family.
- Add review-friendly demo behavior without hidden production bypasses.
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.
- 5d ago First seen · 63 lines · 69 tokens per session scan A 06eecb64160e
ios-app-builder is a skill published in the GitHub repository MartinPuli/createAnApp (14 stars, last pushed 15d ago), licensed MIT. It adds 69 tokens to every session and 668 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 skills, from other repositories
swift-architecture-skill
Swift iOS architecture guidance and playbooks for MVVM, MVI, TCA, Clean Architecture, VIPER, MVP, Coordinator, and Reactive patterns. Use when designing, implementing, refactoring, or reviewing the architecture of a SwiftUI or UIKit feature, module, or codebase.
antigravity-root
Enterprise-grade iOS development workflow for TTBaseUIKit-powered apps. Cross-functional product analysis | MVVM-C Architecture | UIKit + SwiftUI | TTViewCodable | TTBaseSUI | xcodebuild CLI Verification | Zero Regression | iOS 14+.
swiftui-max
Expert SwiftUI guidance for building UI on iOS, iPadOS, macOS, watchOS, tvOS, and visionOS. Use whenever writing, reviewing, refactoring, or debugging ANY SwiftUI code — views, view modifiers, layout, navigation (NavigationStack/SplitView, deep links), lists and scrolling, animation and transitions, state management…
swiftui-compose
Compose Multiplatform ↔ SwiftUI integration patterns. USE FOR: embedding Compose Multiplatform views in a SwiftUI app; embedding SwiftUI/UIKit components inside Compose Multiplatform; sharing state between Compose and SwiftUI; managing the Compose UIViewController lifecycle; bidirectional data flow with the…
SwiftUI Conventions
@State/@Binding/@ObservedObject usage, view composition, preview-driven development.
swift-expert
Expert-level Swift development for iOS, macOS with SwiftUI, Combine, and modern Swift 5.9+. Use when the user mentions iOS, macOS, SwiftUI, Combine, async await, or Apple platforms, or when the task involves Modern Swift Features, Basics and Optionals, Functions and Closures, or Structs and Classes.