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 patrickserrano/lacquer --skill xcode-build-fixergit clone --depth 1 https://github.com/patrickserrano/lacquerWrote 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/patrickserrano/lacquer/xcode-build-fixer)<a href="https://agentmods.dev/skills/patrickserrano/lacquer/xcode-build-fixer"><img src="https://agentmods.dev/badge/skills/patrickserrano/lacquer/xcode-build-fixer.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.00077 | $0.02709 |
| Opus 5 | $0.00039 | $0.01354 |
| Sonnet 5 | $0.00015 | $0.00542 |
| Haiku 4.5 | $0.00008 | $0.00271 |
Grade A, and why
xcode-build-fixer 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 3d 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.
This is a copy
95% identical to xcode-build-fixer — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Xcode Build Fixer
Use this skill to implement approved build optimization changes and verify them with a benchmark.
Core Rules
- Only apply changes that have explicit developer approval.
- Apply one logical fix at a time so changes are reviewable and reversible.
- Re-benchmark after applying changes to verify improvement.
- Report exactly what changed, which files were touched, and the measured delta.
- If a change produces no improvement or causes a regression, flag it immediately.
Inputs
The fixer expects one of:
- An approved optimization plan at
.build-benchmark/optimization-plan.mdwith checked approval boxes. - An explicit developer instruction describing the fix to apply (e.g., "set
DEBUG_INFORMATION_FORMATtodwarffor Debug").
When working from an optimization plan, read the approval checklist and implement only the checked items.
Fix Categories
Build Settings
Change project.pbxproj values to match the recommendations in build-settings-best-practices.md.
Typical fixes:
- Set
DEBUG_INFORMATION_FORMAT = dwarffor Debug - Set
SWIFT_COMPILATION_MODE = singlefilefor Debug - Enable
COMPILATION_CACHE_ENABLE_CACHING = YES - Enable
EAGER_LINKING = YESfor Debug - Align cross-target settings to eliminate module variants
When editing project.pbxproj, locate the correct buildSettings block by matching the target name and configuration name. Verify the change with xcodebuild -showBuildSettings after applying -- FlowDeck has no settings-only inspection equivalent (flowdeck build always performs a real build against a simulator/device destination), so this one call stays raw xcodebuild deliberately.
Script Phases
Fix run script phases that waste time during incremental or debug builds.
Typical fixes:
- Add input and output file declarations so Xcode can skip unchanged scripts.
- Add configuration guards:
[[ "$CONFIGURATION" != "Release" ]] && exit 0for release-only scripts. - Move input/output lists into
.xcfilelistfiles when the list is long. - Enable
Based on dependency analysiswhen inputs and outputs are declared.
What ships with it
4 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.
- 3d ago First seen · 221 lines · 77 tokens per session scan A c5c4b84274ac
xcode-build-fixer is a skill published in the GitHub repository patrickserrano/lacquer (3 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 2,709 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to xcode-build-fixer, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
swiftui-whats-new-27
New SwiftUI APIs, behaviors, and deprecations introduced in the 2027 OS releases (iOS 27, macOS 27, watchOS 27, tvOS 27, visionOS 27). Use when a SwiftUI view using @State fails to compile with "used before being initialized", "invalid redeclaration of synthesized property", or "extraneous argument label" errors after…
expo-modules
Writing Swift/Kotlin native modules with the Expo Modules API, requireNativeModule, async functions, view modules, and the event-emitter pattern. Triggers on expo modules, native module, swift, kotlin, requireNativeModule, expo-module-scripts, expo.modules.json, view module, event emitter, native function, async…
cmp-upgrade
Migrate an existing Kotlin/Compose Multiplatform (CMP/KMP) project to the next PROVEN-GREEN dependency version set. Use this when the user wants to upgrade Kotlin, KSP, Compose Multiplatform, Room, AGP, Koin, or Ktor versions in a KMP project, bump their KMP dependencies, or asks "upgrade kotlin/compose/KMP versions"…
Swift Patterns
Use this skill when working on Swift projects (SwiftPM packages, iOS/macOS apps) and you want consistent patterns for concurrency, structure, and safety.
android-native-dev
Android native application development and UI design guide. Covers Material Design 3, Kotlin/Compose development, project configuration, accessibility, and build troubleshooting. Read this before Android native application development.
modernize-tests
Modernize test suites to use modern Swift Testing features or migrate from XCTest.