Borrowing it
Nothing to install: this file belongs to omarshahine/apple-pim. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/omarshahine/apple-pim/main/.claude/skills/xcode-build-benchmark/SKILL.mdgit clone --depth 1 https://github.com/omarshahine/apple-pimWrote 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/omarshahine/apple-pim/xcode-build-benchmark)<a href="https://agentmods.dev/skills/omarshahine/apple-pim/xcode-build-benchmark"><img src="https://agentmods.dev/badge/skills/omarshahine/apple-pim/xcode-build-benchmark/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/omarshahine/apple-pim/xcode-build-benchmark"><img src="https://agentmods.dev/badge/skills/omarshahine/apple-pim/xcode-build-benchmark.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.00077 | $0.00995 |
| Opus 5.5 | $0.00031 | $0.00398 |
| Sonnet 5.5 | $0.00015 | $0.00199 |
| Haiku 4.5 | $0.00008 | $0.00100 |
Grade A, and why
xcode-build-benchmark 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.
This is a copy
100% identical to xcode-build-benchmark — 0 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Xcode Build Benchmark
Use this skill to produce a repeatable Xcode build baseline before anyone tries to optimize build times.
Core Rules
- Measure before recommending changes.
- Capture clean and incremental builds separately.
- Keep the command, destination, configuration, scheme, and warm-up rules consistent across runs.
- Write a timestamped JSON artifact to
.build-benchmark/. - Do not change project files as part of benchmarking.
Inputs To Collect
Confirm or infer:
- workspace or project path
- scheme
- configuration
- destination
- whether the user wants simulator or device numbers
- whether a custom
DerivedDatapath is needed
If the project has both clean-build and incremental-build pain, benchmark both. That is the default.
Worktree Considerations
When benchmarking inside a git worktree, SPM packages with exclude: paths that reference gitignored directories (e.g., __Snapshots__) will cause xcodebuild -resolvePackageDependencies to crash. Create those missing directories before running any builds.
Default Workflow
- Normalize the build command and note every flag that affects caching or module reuse.
- Run one warm-up build if needed to validate that the command succeeds.
- Run 3 clean builds.
- If
COMPILATION_CACHE_ENABLE_CACHING = YESis detected, run 3 cached clean builds. These measure clean build time with a warm compilation cache -- the realistic scenario for branch switching, pulling changes, or Clean Build Folder. The script handles this automatically by building once to warm the cache, then deleting DerivedData (but not the compilation cache) before each measured run. Pass--no-cached-cleanto skip. - Run 3 zero-change builds (build immediately after a successful build with no edits). This measures the fixed overhead floor: dependency computation, project description transfer, build description creation, script phases, codesigning, and validation. A zero-change build that takes more than a few seconds indicates avoidable per-build overhead. Use the default
benchmark_builds.pyinvocation (no--touch-fileflag). - Optionally run 3 incremental builds with a file touch to measure a real edit-rebuild loop. Use
--touch-file path/to/SomeFile.swiftto touch a representative source file before each build. - Save the raw results and summary into
.build-benchmark/. - Report medians and spread, not just the single fastest run.
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.
- 1mo ago First seen · 89 lines · 77 tokens per session scan A 91b85f1b9b73
xcode-build-benchmark is a skill published in the GitHub repository omarshahine/apple-pim (65 stars, last pushed 6d ago), licensed MIT. It adds 77 tokens to every session and 995 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to xcode-build-benchmark, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
troubleshoot-tcc
A troubleshooting guide for macOS permissions that control access to Calendar and Reminders.
archive-event
Archive a meeting or event into Calendar from a narrative source — a meeting notice, an announcement, a message thread — deriving the time from the thread's authoritative correction, recording the source in the event notes, and labelling any value the source did not state. Use when the user hands over a notice…
calendar-management
Guide for effective use of che-ical-mcp for macOS Calendar & Reminders management. Use when user asks about calendar events, reminders, scheduling, or time management.
rem-cli
Create, list, update, complete, tag, and search macOS Reminders via the rem CLI. Use when the user wants to manage Apple Reminders from the terminal, automate reminder workflows, reference reminders in shell scripts, or schedule anything on macOS.
local-access
A guide for controlling a Mac through local applications such as Calendar, Contacts, Mail, Reminders, Finder, and a web browser. It describes the command format for requesting these actions.
claudexor
Use the local Claudexor control plane for harness-agnostic coding work across Claude Code, Codex, Cursor, and OpenCode. Use when a task benefits from route-aware harness and account selection, quota-aware account rotation, shared thread context, read-only planning or research, best-of-N execution, or cross-harness…