Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/carloshpdoc/ios-workflow-claudenpx agentmods add skills/carloshpdoc/ios-workflow-claude/xcode-compilation-analyzerWrote 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/carloshpdoc/ios-workflow-claude/xcode-compilation-analyzer)<a href="https://agentmods.dev/skills/carloshpdoc/ios-workflow-claude/xcode-compilation-analyzer"><img src="https://agentmods.dev/badge/skills/carloshpdoc/ios-workflow-claude/xcode-compilation-analyzer/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/carloshpdoc/ios-workflow-claude/xcode-compilation-analyzer"><img src="https://agentmods.dev/badge/skills/carloshpdoc/ios-workflow-claude/xcode-compilation-analyzer.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.00074 | $0.01085 |
| Opus 5.5 | $0.00030 | $0.00434 |
| Sonnet 5.5 | $0.00015 | $0.00217 |
| Haiku 4.5 | $0.00007 | $0.00109 |
Grade A, and why
xcode-compilation-analyzer 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-compilation-analyzer — 2 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Xcode Compilation Analyzer
Use this skill when compile time, not just general project configuration, looks like the bottleneck.
Core Rules
- Start from evidence, ideally a recent
.build-benchmark/artifact or raw timing-summary output. - Prefer analysis-only compiler flags over persistent project edits during investigation.
- Rank findings by expected wall-clock impact, not cumulative compile-time impact. When compile tasks are heavily parallelized (sum of compile categories >> wall-clock median), note that fixing individual hotspots may improve parallel efficiency without reducing build wait time.
- When the evidence points to parallelized work rather than serial bottlenecks, label recommendations as "Reduces compiler workload (parallel)" rather than "Reduces build time."
- Do not edit source or build settings without explicit developer approval.
What To Inspect
Build Timing Summaryoutput from clean and incremental builds- long-running
CompileSwiftSourcesor per-file compilation tasks SwiftEmitModuletime -- can reach 60s+ after a single-line change in large modules; if it dominates incremental builds, the module is likely too large or macro-heavyPlanning Swift moduletime -- if this category is disproportionately large in incremental builds (up to 30s per module), it signals unexpected input invalidation or macro-related rebuild cascading- ad hoc runs with:
-Xfrontend -warn-long-expression-type-checking=<ms>-Xfrontend -warn-long-function-bodies=<ms>
- deeper diagnostic flags for thorough investigation:
-Xfrontend -debug-time-compilation-- per-file compile times to rank the slowest files-Xfrontend -debug-time-function-bodies-- per-function compile times (unfiltered, complements the threshold-based warning flags)-Xswiftc -driver-time-compilation-- driver-level timing to isolate driver overhead-Xfrontend -stats-output-dir <path>-- detailed compiler statistics (JSON) per compilation unit for root-cause analysis
- mixed Swift and Objective-C surfaces that increase bridging work
What ships with it
3 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 · 90 lines · 74 tokens per session scan A fc9ce5a59816
xcode-compilation-analyzer is a skill published in the GitHub repository carloshpdoc/ios-workflow-claude (7 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 74 tokens to every session and 1,085 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-compilation-analyzer, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
ia-c-systems
C patterns for systems code, libraries, and native extensions: module layout, function decomposition, status-enum errors, memory safety, undefined behavior, and performance measurement. Use when writing, reviewing, refactoring, or debugging C, working with malloc lifetimes, buffer overflows, sanitizers, or Valgrind…
agent-swift-build-resolver
Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.
rider-search
Routing rules for code search in JetBrains Rider projects — use the Rider MCP symbol/reference/file tools instead of Bash grep. Use whenever searching for a symbol, definition, function, variable, type, or finding usages/references in a C#/.NET or Unreal C++ codebase open in Rider.
swift6-concurrency
Handle Swift 6 concurrency patterns. Use when encountering Sendable warnings, data race errors, MainActor isolation issues, or framework interop problems (EventKit, Speech, AVFoundation, etc.). Trigger on "Swift 6 error", "Sendable", "data race", "MainActor", "concurrency warning", or "strict concurrency".
agent-kotlin-build-resolver
Kotlin/Gradle build, compilation, and dependency error resolution specialist. Fixes build errors, Kotlin compiler errors, and Gradle issues with minimal changes. Use when Kotlin builds fail.
ia-cpp-systems
Modern C++ patterns: RAII and ownership, rule of zero/five, exceptions and error handling, API and ABI boundaries, templates, and CMake tooling. Use when writing, reviewing, refactoring, or debugging C++, working with smart pointers, move semantics, memory leaks, template errors, or gtest. For plain C, see…