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 SwiftfulThinking/SwiftfulStarterProject --skill creating-modulegit 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/skills/swiftfulthinking/swiftfulstarterproject/creating-module)<a href="https://agentmods.dev/skills/swiftfulthinking/swiftfulstarterproject/creating-module"><img src="https://agentmods.dev/badge/skills/swiftfulthinking/swiftfulstarterproject/creating-module.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.00078 | $0.01661 |
| Opus 5 | $0.00039 | $0.00830 |
| Sonnet 5 | $0.00016 | $0.00332 |
| Haiku 4.5 | $0.00008 | $0.00166 |
Grade A, and why
creating-module 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Module
Add a new top-level navigation module to the app. Modules replace the entire screen hierarchy — they are not pushed or presented, they swap the whole view tree.
Existing Modules
The app ships with two modules:
| Module | ID | Content |
|---|---|---|
| Onboarding | Constants.onboardingModuleId |
onboardingFlow() — WelcomeView → sign in/up → OnboardingCompletedView |
| Tabbar | Constants.tabbarModuleId |
coreModuleTabBarView() — TabBarView with Home, Beta, Profile tabs |
ModuleWrapperView
Every module is wrapped in a ModuleWrapperView — a shared component that provides deep link (.onOpenURL) and push notification (.onNotificationReceived) handling at the module level.
Files — Core/ModuleWrapper/:
| File | Purpose |
|---|---|
ModuleWrapperView.swift |
View wrapper + ModuleWrapperDelegate struct + CoreBuilder extension |
ModuleWrapperPresenter.swift |
Handles deep link and push notification routing |
ModuleWrapperInteractor.swift |
Protocol extending GlobalInteractor |
ModuleWrapperRouter.swift |
Protocol extending GlobalRouter |
ModuleWrapperDelegate carries the moduleId: String so deep link/push handlers know which module is active and can route accordingly.
WARNING: ModuleWrapperView does NOT have a NavigationStack. The presenter cannot use router.showScreen(.push). It can use .fullScreenCover, .sheet, showModal, showAlert, update interactor state, or post a notification. See the adding-deep-link skill for details.
The ModuleWrapper already exists in the starter project — you do not need to create it. You only need to wrap your module's content with moduleWrapperView(router:delegate:).
Steps
- Get the module name and purpose from the user (camelCase for ID, e.g.,
"admin","settings") - Add the module ID constant
- Create the entry view builder method
- Create the switch method on CoreRouter
- Add the starting module case in AppView (if applicable)
- Create the module's root content
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 · 173 lines · 78 tokens per session scan A b2c05d2fd05a
creating-module is a skill published in the GitHub repository SwiftfulThinking/SwiftfulStarterProject (74 stars, last pushed 5mo ago), licensed MIT. It adds 78 tokens to every session and 1,661 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-04.
Other skills, from other repositories
orca-emulator-android
Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.
apple-search-ads
When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT"…
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.