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-view-modifiergit 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-view-modifier)<a href="https://agentmods.dev/skills/swiftfulthinking/swiftfulstarterproject/creating-view-modifier"><img src="https://agentmods.dev/badge/skills/swiftfulthinking/swiftfulstarterproject/creating-view-modifier.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.00072 | $0.00914 |
| Opus 5 | $0.00036 | $0.00457 |
| Sonnet 5 | $0.00014 | $0.00183 |
| Haiku 4.5 | $0.00007 | $0.00091 |
Grade A, and why
creating-view-modifier 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 2d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating View Modifier
Scaffold a ViewModifier struct with a View extension in Components/ViewModifiers/.
Steps
- Get the modifier name and purpose from the user
- Determine the file name (see naming below)
- Create the ViewModifier struct
- Add a View extension method
- Add
#Previewblocks demonstrating usage
File Location
All view modifiers go in Components/ViewModifiers/:
Components/ViewModifiers/{Name}ViewModifier.swift
If a file contains multiple related modifiers (e.g., button styles), name it by the group:
Components/ViewModifiers/ButtonViewModifiers.swift
Template — Single Modifier
import SwiftUI
struct {Name}ViewModifier: ViewModifier {
// Parameters — use defaults where possible
let title: String
var isEnabled: Bool = true
func body(content: Content) -> some View {
content
// Apply transformations to content
}
}
extension View {
func {modifierName}(title: String, isEnabled: Bool = true) -> some View {
modifier({Name}ViewModifier(title: title, isEnabled: isEnabled))
}
}
#Preview {
Text("Hello, world!")
.padding()
.{modifierName}(title: "Example")
}
Template — Modifier with State
For modifiers that track internal state (e.g., first appear, animation):
import SwiftUI
struct {Name}ViewModifier: ViewModifier {
@State private var didAppear: Bool = false
let action: () -> Void
func body(content: Content) -> some View {
content
.onAppear {
guard !didAppear else { return }
didAppear = true
action()
}
}
}
extension View {
func {modifierName}(action: @escaping () -> Void) -> some View {
modifier({Name}ViewModifier(action: action))
}
}
Template — ButtonStyle (Related Pattern)
Custom button styles are not ViewModifier but follow the same file location and grouping:
import SwiftUI
struct {Name}ButtonStyle: ButtonStyle {
func makeBody(configuration: Configuration) -> some View {
configuration.label
.scaleEffect(configuration.isPressed ? 0.95 : 1)
.animation(.smooth, value: configuration.isPressed)
}
}
extension View {
func {styleName}Button(action: @escaping () -> Void) -> some View {
Button(action: action) { self }
.buttonStyle({Name}ButtonStyle())
}
}
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.
- 2d ago First seen · 131 lines · 72 tokens per session scan A 42f20f0de0f4
creating-view-modifier is a skill published in the GitHub repository SwiftfulThinking/SwiftfulStarterProject (74 stars, last pushed 5mo ago), licensed MIT. It adds 72 tokens to every session and 914 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
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…
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.
platform-conventions
Design to iOS and Android conventions — what each OS mandates, where they diverge, and when to unify. Use when shipping native apps. For breakpoint adaptation use responsive-design; for matching competitor patterns use jakobs-law (interaction-design).
field-service-mobile-branding-configure
Derive a Field Service mobile app color scheme from a brand source (URL, hex codes, brand-guide paste, or color description), validate WCAG AA contrast in both light and dark mode, and apply the 14-field scheme to the org-default FieldServiceMobileSettings record. Trigger phrases include 'brand the mobile app', 'apply…
app-ui-design
Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.