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 agentmods add skills/firebase/agent-skills/xcode-project-setupnpx skills add firebase/agent-skills --skill xcode-project-setupgit clone --depth 1 https://github.com/firebase/agent-skillsWhat 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 | $0.00046 | $0.01424 |
| Opus 5 | $0.00023 | $0.00712 |
| Sonnet 5 | $0.00009 | $0.00285 |
| Haiku 4.5 | $0.00005 | $0.00142 |
Grade A, and why
xcode-project-setup 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- xcode-project-setup — 98% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Xcode Project Setup
⛔️ CRITICAL RULES & ENVIRONMENT CHECKS
Before performing any Xcode setup or file manipulation, you MUST adhere to the following rules. A hefty fee will be applied if you violate them.
1. The Anti-Ruby Mandate
You are strictly forbidden from using Ruby, Rails, or any Ruby gems
(including the xcodeproj gem). Under no circumstances may you write or execute
Ruby scripts.
2. Modern Xcode Folder Synchronization
Modern Xcode projects support folder synchronization. When adding new source
code (.swift) or resource files, simply write them to the correct directory on
disk. They will be automatically included in the Xcode project. Never manually
modify the .pbxproj file to add files.
3. Allowed Scripting Languages
If you absolutely must write a script to manipulate the project environment
(e.g., configuring SPM packages beyond what the provided xcode_spm_setup
script does), you must use Swift. Only as an absolute last resort, if Swift
is completely unviable, may you use Node.js or TypeScript.
4. Toolchain Verification
Because this skill relies entirely on a native Swift script, you must verify the environment:
- Run
swift --versionbefore proceeding. - If the Swift command is not found, you must stop and recommend the user
install the Swift toolchain (e.g., via
xcode-select --installon macOS), or ask if you can attempt to install it for them. Do not attempt to proceed without Swift.
5. Mandatory Linker Flags for Static Frameworks (Firebase)
When setting up SPM dependencies that heavily rely on internal Objective-C
categories and +load methods (such as the Firebase iOS SDK suite), the Apple
linker will aggressively strip these methods out if they are linked statically.
This causes fatal runtime crashes (e.g.,
FirebaseAuth/Auth.swift:167: Fatal error: Unexpectedly found nil).
The provided xcode_spm_setup Swift script automatically injects the -ObjC
flag to OTHER_LDFLAGS when adding Firebase products. However, you should
still verify it is present in the build settings if you encounter issues.
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.
- 2d ago First seen · 143 lines · 46 tokens per session scan A 3a7f5e3b2886
xcode-project-setup is a skill published in the GitHub repository firebase/agent-skills (430 stars, last pushed 5d ago), licensed Apache-2.0. It adds 46 tokens to every session and 1,424 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
kotlin-specialist
Provides idiomatic Kotlin implementation patterns including coroutine concurrency, Flow stream handling, multiplatform architecture, Compose UI construction, Ktor server setup, and type-safe DSL design. Use when building Kotlin applications requiring coroutines, multiplatform development, or Android with Compose.…
expo-module
Framework (OSS). Guide for creating and writing Expo native modules and views using the Expo Modules API (Swift, Kotlin, TypeScript). Covers module definition DSL, native views, shared objects, config plugins, lifecycle hooks, autolinking, and type system. Use when building or modifying native modules for Expo. Not…
swiftui-dev
Use this skill for SwiftUI development, architecture, structure, performance, and Apple native app profiling. It combines.
compose-state-holder-ui-split
Use when a Jetpack Compose screen-level composable takes a ViewModel/component/controller, collects state or effects, handles navigation/snackbars, or wires callbacks while also rendering layout. Technique-layer skill — complements the codebase-specific compose-expert and feed-patterns.
ios-product-dev
Own end-to-end native iOS product work in SwiftUI: shape, implement, and verify beautiful, accessible Companion features while preserving the shared API and platform boundaries. Use for iOS feature work, product-facing UI changes, and native client reviews; route pure visual design or build-only requests to the…
build-feature
Build an iOS feature using ShipSwift components. Use when the user says "build", "create", "add a feature", or describes an iOS feature they want to implement.