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-componentgit 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-component)<a href="https://agentmods.dev/skills/swiftfulthinking/swiftfulstarterproject/creating-component"><img src="https://agentmods.dev/badge/skills/swiftfulthinking/swiftfulstarterproject/creating-component/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/swiftfulthinking/swiftfulstarterproject/creating-component"><img src="https://agentmods.dev/badge/skills/swiftfulthinking/swiftfulstarterproject/creating-component.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.00057 | $0.00794 |
| Opus 5.5 | $0.00023 | $0.00318 |
| Sonnet 5.5 | $0.00011 | $0.00159 |
| Haiku 4.5 | $0.00006 | $0.00079 |
Grade A, and why
creating-component 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 1mo 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Component
Scaffold a reusable SwiftUI component — pure UI with injected data and actions.
Steps
- Get the component name from the user (PascalCase, must end in
View— e.g., "ProfileCardView", "LoadingSpinnerView", "CustomModalView") - Determine the subfolder (see below)
- Create a single file:
{ComponentName}View.swift - Add multiple
#Previewblocks for different states
Folder Location
Screen-specific components — used by only one screen — go inside that screen's folder:
Core/{ScreenName}/Components/{ScreenName}HeaderView.swift
Generic/reusable components — used across multiple screens — go in the shared Components folder:
Components/Views/StretchyHeaderView.swift
Components/Modals/CustomModalView.swift
Components/Images/ImageLoaderView.swift
Components/ViewModifiers/ButtonViewModifiers.swift
| Subfolder | Use For |
|---|---|
Views/ |
General reusable views (DEFAULT) |
Modals/ |
Modal/popup overlay components |
Images/ |
Image-related components |
ViewModifiers/ |
ViewModifier structs |
If unclear, ask the user whether the component is screen-specific or reusable.
Component Rules
- No business logic — pure UI rendering only
- No
@Statefor data — only@State private varfor local UI animation state - No
@Observableobjects, no Presenters — components are not VIPER modules - All data injected via
varproperties with default values — notlet, so the implicit init has defaults - Make as much as possible optional — unwrap in the view body
- All actions are closures with defaults — e.g.,
var onTap: () -> Void = { } import SwiftfulUIwhen using.asButton(),.tappableBackground(),.ifSatisfiesCondition(), or other SwiftfulUI extensions- Follow the
swiftui-patternsrules for layout, buttons, images, text
Template
import SwiftUI
import SwiftfulUI
struct {ComponentName}View: View {
var title: String? = nil
var subtitle: String? = nil
var onTap: () -> Void = { }
var body: some View {
VStack(spacing: 8) {
if let title {
Text(title)
.font(.headline)
}
if let subtitle {
Text(subtitle)
.font(.subheadline)
.foregroundStyle(.secondary)
}
}
.asButton(.press) {
onTap()
}
}
}
#Preview("Full Data") {
{ComponentName}View(
title: "Title",
subtitle: "Subtitle",
onTap: { }
)
}
#Preview("Title Only") {
{ComponentName}View(
title: "Title"
)
}
#Preview("Empty") {
{ComponentName}View()
}
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.
- 1mo ago First seen · 109 lines · 57 tokens per session scan A e7e2dcd31592
creating-component is a skill published in the GitHub repository SwiftfulThinking/SwiftfulStarterProject (74 stars, last pushed 7d ago), licensed MIT. It adds 57 tokens to every session and 794 once invoked, about $0.0002 per session on Opus 5.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
glance-canonical-layouts
Use this skill to create home screen widgets using Jetpack Glance Canonical Layouts from the Android Platform Samples project, or when asked to implement standard widget layout patterns (including Check List, Image Grid, Snap Scrolling, and Standard Toolbar).
display-glasses-with-jetpack-compose-glimmer
Provides guidelines for developing projected Android XR apps for display glasses using the Jetpack Compose Glimmer UI toolkit. Covers Glimmer design principles, workflows, and interaction models for the glasses form factor. Use this skill to build an Android XR Augmented Experience app with Jetpack Compose Glimmer.…
expo-design-system
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 creating or organizing…
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.
axiom-audit-liquid-glass
Use when the user mentions Liquid Glass review, iOS 26 UI updates, toolbar improvements, or visual effect migration.
omh-apple-design
This is an OMH apple-design workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).