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 JakubMikolajek/codex-skills-collection --skill swiftuigit clone --depth 1 https://github.com/JakubMikolajek/codex-skills-collectionWrote 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/jakubmikolajek/codex-skills-collection/swiftui)<a href="https://agentmods.dev/skills/jakubmikolajek/codex-skills-collection/swiftui"><img src="https://agentmods.dev/badge/skills/jakubmikolajek/codex-skills-collection/swiftui/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/jakubmikolajek/codex-skills-collection/swiftui"><img src="https://agentmods.dev/badge/skills/jakubmikolajek/codex-skills-collection/swiftui.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.00077 | $0.01455 |
| Opus 5 | $0.00039 | $0.00727 |
| Sonnet 5 | $0.00015 | $0.00291 |
| Haiku 4.5 | $0.00008 | $0.00145 |
Grade A, and why
swiftui 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 11d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SwiftUI Implementation Patterns
Use this skill to keep SwiftUI changes composable, state-safe, and aligned with iOS 17+, MVVM, the new Observation APIs, and Factory for dependency injection.
Delivery Workflow
Use the checklist below and track progress:
SwiftUI progress:
- [ ] Step 1: Discover project conventions and navigation model
- [ ] Step 2: Map screen state, ViewModel ownership, and Factory dependencies
- [ ] Step 3: Compose views into small reusable units
- [ ] Step 4: Wire Observation-based bindings and async work safely
- [ ] Step 5: Verify accessibility, previews, and tests
Platform Assumptions
- Target iOS 17+ by default.
- Prefer the modern Observation model over legacy
ObservableObjectpatterns unless the project still depends on older code paths. - Do not add compatibility fallbacks for pre-iOS 17 APIs unless the repository explicitly requires them.
State Management Rules
- Keep
Viewtypes focused on presentation and lightweight interaction wiring. - Prefer one clear source of truth for screen state.
- Treat the
ViewModelas the owner of screen business state in MVVM flows. - Use the project's existing observation model first; do not mix competing patterns without a reason.
- Keep transient UI state local to the view and move shared/business state into an observable
ViewModel. - Derive display values from state instead of duplicating them.
Property Wrapper Guidance
| Use case | Preferred approach |
|---|---|
| View-local ephemeral state | @State |
| Child edits parent-owned state | @Binding |
| View binds into an observable model | @Bindable where binding into Observation-backed state is needed |
| View owns lifecycle of observable model | Instantiate or inject the MVVM ViewModel using the project-standard ownership pattern |
| View receives externally owned observable model | Keep ownership upstream and pass the model intentionally |
| Global shared dependencies | Factory-backed injection or existing environment pattern only when already established |
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.
- 11d ago First seen · 149 lines · 77 tokens per session scan A 4efa47ef99b9
swiftui is a skill published in the GitHub repository JakubMikolajek/codex-skills-collection (5 stars, last pushed 5d ago), licensed MIT. It adds 77 tokens to every session and 1,455 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-08-31.
Other skills, from other repositories
expo-design-system
Framework (OSS). Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow, motion), reusable component structure with variant/size/state prop conventions, and rules for when to extract a repeated view into a shared component. Use when…
flutter-build-responsive-layout
Use LayoutBuilder, MediaQuery, or Expanded/Flexible to create a layout that adapts to different screen sizes. Use when you need the UI to look good on both mobile and tablet/desktop form factors.
display-glasses-with-jetpack-compose-glimmer
Provides guidelines for developing projected Android XR apps for display glasses using the Jetpack Compose Glimmer UI toolkit. This skill covers foundational Glimmer design principles, workflows for implementing Jetpack Compose Glimmer, and interaction models for the glasses form factor. Use this skill to build an…
omh-apple-design
This is a Hermes-native apple-design workflow skill.
axiom-audit-liquid-glass
Use when the user mentions Liquid Glass review, iOS 26 UI updates, toolbar improvements, or visual effect migration.
axiom-audit-ux-flow
Use 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.