add-component

add-component is a skill for Claude Code, Codex from signerlabs/ShipSwift. It costs 48 tokens per session (458 once invoked), scanned A, original, MIT.

A skill for adding ready-made SwiftUI interface components from the ShipSwift source library to an Apple-platform project. SwiftUI is Apple's framework for building app interfaces in Swift.

In plain words
What is it for?
Use it to add elements such as loading effects, charts, alerts, login flows, or camera features, then adapt their names, colors, data, and dependencies to the project.
Why use it?
It avoids recreating common interface pieces from scratch and helps identify the source files and supporting utilities they need. It also accounts for platform-specific files and project setup.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to add elements such as loading effects, charts, alerts, login…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/signerlabs/shipswift/add-component
About the project

signerlabs/ShipSwift is a SwiftUI component library that also provides full-stack app recipes and an MCP server for AI coding tools. It helps developers and coding agents build iOS applications using reusable interface components and documented implementation patterns. The catalogue entries provide the skills, instructions, and MCP access needed to use ShipSwift with compatible agents.

signerlabs/ShipSwift · 2,983 stars · on GitHub · shipswift.app

Install

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.

Any agent
npx skills add signerlabs/ShipSwift --skill add-component
Clone the repo
git clone --depth 1 https://github.com/signerlabs/ShipSwift

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for add-component

README.md
[![agentmods](https://agentmods.dev/badge/skills/signerlabs/shipswift/add-component.svg)](https://agentmods.dev/skills/signerlabs/shipswift/add-component)
Your own site
<a href="https://agentmods.dev/skills/signerlabs/shipswift/add-component"><img src="https://agentmods.dev/badge/skills/signerlabs/shipswift/add-component.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 458 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.00458
Opus 5 $0.00024 $0.00229
Sonnet 5 $0.00010 $0.00092
Haiku 4.5 $0.00005 $0.00046

Measured 7d ago against content hash d82b8c2cfb65, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

add-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 7d 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.

skills/add-component/SKILL.md · 39 lines

What it actually says

Add Component from ShipSwift

Add production-ready SwiftUI components to your project from ShipSwift's local source library.

Workflow

  1. Identify the component: Read skills/catalog.md to find the right component. Common mappings:

    • "shimmer" / "loading skeleton" → SWAnimation/SWShimmer.swift
    • "donut chart" / "pie chart" → SWChart/SWDonutChart.swift
    • "alert" / "popup" → SWComponent/Feedback/SWAlert.swift
    • "auth" / "login" → SWModule/SWAuth/ (all files)
    • "camera" → SWModule/SWCamera/ (all files)
  2. Read the source file: Read the Swift file from ShipSwift/SWPackage/<path>. The file contains the complete implementation.

  3. Integrate into the project:

    • Copy the file(s) into the user's project
    • Also copy SWUtil/ if not already present
    • Adapt naming, colors, and data models to match the project
    • For +iOS/+macOS files, set the platform filter in Xcode Build Phases
  4. Verify: Walk through any dependencies or setup steps needed.

Guidelines

  • Types use SW prefix (SWDonutChart, SWTypewriter).
  • View modifiers use .sw prefix (.swShimmer(), .swGlowScan()).
  • Chart components use a generic CategoryType pattern with String convenience initializer.
  • Internal helper types should be private with SW prefix.
  • Components in SWAnimation/, SWChart/, and SWComponent/ are each self-contained (single file + SWUtil).
  • Modules in SWModule/ are multi-file — copy the entire folder.
Changes

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.

  1. 7d ago First seen · 39 lines · 48 tokens per session scan A d82b8c2cfb65

Subscribe to this mod's changes

add-component is a skill published in the GitHub repository signerlabs/ShipSwift (2,983 stars, last pushed 28d ago), licensed MIT. It adds 48 tokens to every session and 458 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

mobile-app

A design template for a single-screen iPhone 15 Pro app mockup, including the phone frame, status bar, app header, main content, and bottom navigation.

nexu-io/html-anything · 21 tokens

mobile-onboarding

A visual template showing three mobile-app onboarding screens side by side: a splash screen, a feature introduction, and sign-in.

nexu-io/html-anything · 18 tokens

iOS SwiftUI Accessibility

Enforces WCAG 2.2 accessible coding patterns when writing SwiftUI — labels, traits, Dynamic Type, contrast, touch targets, focus management, orientation, and more. Based on the ios-swiftui-accessibility-techniques project with 41 static analysis rules across 23 WCAG criteria.

cvs-health/ios-swiftui-accessibility-techniques · 67 tokens

maui-accessibility

Improve MAUI accessibility. USE FOR: semantic labels, hints, headings, screen-reader focus/announcements, AutomationProperties, touch targets, decorative content, TalkBack/VoiceOver/Narrator checks. DO NOT USE FOR: general layout, automation-only tests, performance.

dotnet/maui-labs · 60 tokens

ui-enhancer-radar

Systematic iOS/SwiftUI UI audit with design intent interview, 14-domain analysis (including Color Audit with adaptive Color Profile, iPad Sheet Sizing caller-side audit, Button Hit Region three-factor interaction audit, and Silent Picker menu-presentation audit), element compaction, cross-view consistency checks…

Terryc21/radar-suite · 148 tokens

ui-path-radar

UI path tracer for SwiftUI/UIKit apps. 5-layer audit with 34 issue categories and 19 automated checks: discover entry points, trace flows, detect dead ends and broken promises, evaluate UX impact, verify data wiring. Supports targeted trace, diff against previous audits, and handoff to planning skills. Triggers…

Terryc21/radar-suite · 86 tokens