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/swiftfulthinking/swiftfulstarterproject/refactoring-screennpx skills add SwiftfulThinking/SwiftfulStarterProject --skill refactoring-screengit 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/refactoring-screen)<a href="https://agentmods.dev/skills/swiftfulthinking/swiftfulstarterproject/refactoring-screen"><img src="https://agentmods.dev/badge/skills/swiftfulthinking/swiftfulstarterproject/refactoring-screen.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.00063 | $0.00992 |
| Opus 5 | $0.00032 | $0.00496 |
| Sonnet 5 | $0.00013 | $0.00198 |
| Haiku 4.5 | $0.00006 | $0.00099 |
Grade A, and why
refactoring-screen 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactoring Screen
Rename a VIPER screen across all files. This is a mechanical find-and-replace across 4+ files, plus cross-references.
Steps
- Get the current screen name and new screen name (PascalCase, e.g.,
Home→Dashboard) - Search for all references to the old name across the codebase
- Rename files and folder
- Update all internal references
- Update all cross-references from other screens
Files to Update
Every screen has 4 files in Core/{ScreenName}/:
| File | Contains |
|---|---|
{ScreenName}View.swift |
View struct, Delegate struct, CoreBuilder extension, CoreRouter extension |
{ScreenName}Presenter.swift |
Presenter class, Event enum with event name strings |
{ScreenName}Interactor.swift |
Interactor protocol, CoreInteractor conformance |
{ScreenName}Router.swift |
Router protocol, CoreRouter conformance |
What to Rename
In all 4 files — replace {OldName} with {NewName}:
- Struct/class/protocol names:
{OldName}View,{OldName}Presenter,{OldName}Interactor,{OldName}Router - Delegate struct:
{OldName}Delegate - Builder method:
func {oldName}View(→func {newName}View( - Router method:
func show{OldName}View(→func show{NewName}View(
In Presenter — update event name strings:
// Old:
return "{OldName}View_Appear"
return "{OldName}View_Disappear"
// New:
return "{NewName}View_Appear"
return "{NewName}View_Disappear"
Navigation title (if applicable):
// Old:
.navigationTitle("{OldName}")
// New:
.navigationTitle("{NewName}")
Rename files:
{OldName}View.swift→{NewName}View.swift{OldName}Presenter.swift→{NewName}Presenter.swift{OldName}Interactor.swift→{NewName}Interactor.swift{OldName}Router.swift→{NewName}Router.swift
Rename folder:
Core/{OldName}/→Core/{NewName}/
Screen-specific components (if they exist):
If Core/{OldName}/Components/ exists, rename the folder and update any component names that include the old screen name.
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 · 113 lines · 63 tokens per session scan A e05ce3916129
refactoring-screen is a skill published in the GitHub repository SwiftfulThinking/SwiftfulStarterProject (74 stars, last pushed 5mo ago), licensed MIT. It adds 63 tokens to every session and 992 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-09-04.
Other skills, from other repositories
wear-compose-m3
Expert guidance for working with Wear OS Compose Material3. Use this skill when creating, updating, or migrating Wear OS projects. This includes the androidx.wear.compose.material3, androidx.wear.compose.foundation, and androidx.wear.compose.navigation3 libraries. Also working with core components such as AppScaffold…
kotlin-specialist
Provides idiomatic Kotlin implementation patterns including coroutine concurrency, Flow stream handling, multiplatform architecture, Compose UI construction, Ktor server setup, and type-safe DSL design. Use when building Kotlin applications requiring coroutines, multiplatform development, or Android with Compose.…
build-android-binary
Compile a PAM control's Android Kotlin module into the runtime-loadable DEX for a .ppmplugin. Creates a staged Gradle build with the pinned wrapper and react-android compile dependency, verifies manifest/module/package alignment and runtime-loading constraints, builds the release AAR, then runs d8 --min-api 24. Writes…
swiftui-dev
Use this skill for SwiftUI development, architecture, structure, performance, and Apple native app profiling. It combines.
android-navigation-3
Install and migrate to Jetpack Navigation 3. Use when implementing Navigation 3 patterns including NavDisplay, NavKey routes, deep links, multiple backstacks, scenes (dialogs, bottom sheets), or migrating from Navigation 2.
mobiai-kmp
Use when working on a Kotlin Multiplatform project — shared code, expect/actual declarations, platform-specific implementations, building and testing.