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.
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 signerlabs/ShipSwift --skill add-componentgit clone --depth 1 https://github.com/signerlabs/ShipSwiftWrote 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/signerlabs/shipswift/add-component)<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>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.00048 | $0.00458 |
| Opus 5 | $0.00024 | $0.00229 |
| Sonnet 5 | $0.00010 | $0.00092 |
| Haiku 4.5 | $0.00005 | $0.00046 |
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.
What it actually says
Add Component from ShipSwift
Add production-ready SwiftUI components to your project from ShipSwift's local source library.
Workflow
-
Identify the component: Read
skills/catalog.mdto 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)
- "shimmer" / "loading skeleton" →
-
Read the source file: Read the Swift file from
ShipSwift/SWPackage/<path>. The file contains the complete implementation. -
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/+macOSfiles, set the platform filter in Xcode Build Phases
-
Verify: Walk through any dependencies or setup steps needed.
Guidelines
- Types use
SWprefix (SWDonutChart,SWTypewriter). - View modifiers use
.swprefix (.swShimmer(),.swGlowScan()). - Chart components use a generic
CategoryTypepattern withStringconvenience initializer. - Internal helper types should be
privatewithSWprefix. - Components in
SWAnimation/,SWChart/, andSWComponent/are each self-contained (single file + SWUtil). - Modules in
SWModule/are multi-file — copy the entire folder.
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.
- 7d ago First seen · 39 lines · 48 tokens per session scan A d82b8c2cfb65
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.
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.
mobile-onboarding
A visual template showing three mobile-app onboarding screens side by side: a splash screen, a feature introduction, and sign-in.
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.
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.
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…
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…