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 memi-design/design-skills --skill xcode-build-reliabilitygit clone --depth 1 https://github.com/memi-design/design-skillsWrote 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/memi-design/design-skills/xcode-build-reliability)<a href="https://agentmods.dev/skills/memi-design/design-skills/xcode-build-reliability"><img src="https://agentmods.dev/badge/skills/memi-design/design-skills/xcode-build-reliability/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/memi-design/design-skills/xcode-build-reliability"><img src="https://agentmods.dev/badge/skills/memi-design/design-skills/xcode-build-reliability.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.00036 | $0.00305 |
| Opus 5.5 | $0.00014 | $0.00122 |
| Sonnet 5.5 | $0.00007 | $0.00061 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
xcode-build-reliability 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.
What it actually says
Xcode Build Reliability
Workflow
- Discover the workspace/project and shared schemes with
xcodebuild -list -json; never guess names. - Inspect build settings for the selected scheme and configuration.
- Pin an explicit simulator destination or generic device destination.
- Put canonical commands in an existing Makefile, script, or task runner only when the repository lacks one. Keep local and CI commands aligned.
- Pipe output through
xcbeautifywhen installed, while preservingpipefailand the originalxcodebuildexit status. - Store DerivedData and result bundles in known paths for repeatability and cleanup.
- Measure build-time work before changing settings. Avoid global optimizations that weaken correctness or diagnostics.
- End with a clean build, incremental build, test, and archive/signing status receipt as applicable.
Safety
- Do not delete shared signing, provisioning, or project settings to make a local build pass.
- Do not add generated user data or local absolute paths to source control.
- Do not change warnings or concurrency errors into ignored diagnostics.
- Do not claim archive, signing, notarization, or App Store readiness from a simulator build.
Read references/command-contract.md for the shell contract.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 27 lines · 36 tokens per session scan A 366e8e453912
xcode-build-reliability is a skill published in the GitHub repository memi-design/design-skills (7 stars, last pushed 27d ago), licensed MIT. It adds 36 tokens to every session and 305 once invoked, about $0.0001 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-03.
Other skills, from other repositories
swiftui-native-first
The single most important quality skill. Enforces native SwiftUI components and rejects unnecessary custom code. Use this skill as a reference throughout the entire build process. Include its core rules in every CLAUDE.md. This is what prevents Claude Code from building janky custom UI when a native component exists.
uikit-bridging
How to bridge UIKit into a SwiftUI app correctly when SwiftUI's API is genuinely insufficient. Covers UIViewRepresentable lifecycle, sizeThatFits, font-design inheritance, animation suppression, and the small set of legitimate use cases. Use this skill whenever the swiftui-native-first skill points you here for a…
dark-mode-legibility
Test every screen in BOTH light and dark mode every iteration. The most common iOS legibility bugs only show in one mode, including a specific class of vibrancy-on-pastel-tint failures that produce illegible labels on glass buttons. Use this skill alongside polish-and-refinement during the polish phase, and as a…
pixel-and-stroke-geometry
How strokes, anti-aliasing, and pixel boundaries actually behave in SwiftUI Canvas and Shape rendering. Covers stroke centering, inset-vs-outset, anti-alias-induced flicker on animating strokes, and 1pt vs 0.5pt strokes on retina displays. Use this skill for any app that draws on a grid or canvas — pattern designers…
polish-and-refinement
Take a working app from "it works" to "it feels right." Covers Figma matching, Liquid Glass, animations, haptics, dark mode, and the subjective quality that separates a good app from a great one. Use this skill after all screens are built and data persistence is working. This is where Figma enters the workflow if you…
post-launch
Everything that happens after v1 ships. Crash reporting setup, TestFlight feedback processing, version management, the update cycle, and how to maintain an app without breaking what already works. Use this skill after your first App Store submission and for all subsequent updates.