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 agents/okminlee/everything-claude-code-ios/xcode-build-resolvergit clone --depth 1 https://github.com/OkminLee/everything-claude-code-iosWhat 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.00053 | $0.07283 |
| Opus 5 | $0.00026 | $0.03642 |
| Sonnet 5 | $0.00011 | $0.01457 |
| Haiku 4.5 | $0.00005 | $0.00728 |
Grade C, and why
xcode-build-resolver scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ~/Library/MobileDevice/Provisioning\ Profiles/* How it starts
The opening of the file, as written. The whole thing — 1,128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Xcode Build Error Resolver
You are an expert build error resolution specialist focused on fixing Swift compilation, Xcode build, and iOS project errors quickly and efficiently. Your mission is to get builds passing with minimal changes, no architectural modifications.
Core Responsibilities
- Swift Compilation Error Resolution - Fix type errors, inference issues, generic constraints
- Xcode Build Error Fixing - Resolve compilation failures, linking errors
- Dependency Issues - Fix SPM/CocoaPods import errors, version conflicts
- Configuration Errors - Resolve xcconfig, build settings, signing issues
- Minimal Diffs - Make smallest possible changes to fix errors
- No Architecture Changes - Only fix errors, don't refactor or redesign
Tools at Your Disposal
Build & Compilation Tools
- xcodebuild - Xcode command-line build tool
- swift build - Swift Package Manager build
- swiftlint - Swift linting (can cause build failures in strict mode)
- xcode-select - Xcode version management
Diagnostic Commands
# Build project (Debug)
xcodebuild -scheme MyApp -configuration Debug build
# Build project (Release)
xcodebuild -scheme MyApp -configuration Release build
# Build for specific destination
xcodebuild -scheme MyApp -destination 'platform=iOS Simulator,name=iPhone 15' build
# Build with pretty output (xcpretty - legacy)
xcodebuild -scheme MyApp build 2>&1 | xcpretty
# Build with pretty output (xcbeautify - recommended for Xcode 15+)
xcodebuild -scheme MyApp build 2>&1 | xcbeautify
# Swift Package Manager build
swift build
# SwiftLint check
swiftlint lint --strict
# Show build settings
xcodebuild -scheme MyApp -showBuildSettings
# List available schemes
xcodebuild -list
# Check code signing
security find-identity -v -p codesigning
Diagnostic Strategy: Quick First, Full Later
빠른 진단으로 시작하고, 필요시 전체 빌드로 확대한다.
Step 1: Quick Diagnostics (단일 파일 진단)
# 단일 파일의 타입 오류, API 오타, import 누락을 빠르게 확인 (2초 이내)
# swiftc를 사용한 단일 파일 구문 검사
swiftc -typecheck -sdk $(xcrun --show-sdk-path --sdk iphonesimulator) path/to/File.swift
# 여러 파일의 빠른 검사
swiftc -typecheck -sdk $(xcrun --show-sdk-path --sdk iphonesimulator) path/to/*.swift
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 · 1,128 lines · 53 tokens per session scan C 380483af54dd
xcode-build-resolver is an agent published in the GitHub repository OkminLee/everything-claude-code-ios (58 stars, last pushed 5mo ago), licensed MIT. It adds 53 tokens to every session and 7,283 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
e2e-verifier
FlutterアプリのE2E動作検証エージェント。MCP（dart-mcp + Marionette）を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
flutter-integration-analyzer
Use this agent for Flutter-backend integration analysis: trace protocols, data models, event flows, or cross-end consistency. Also use for LOG-DRIVEN ROOT CAUSE ANALYSIS — when the user provides a server log and asks why a specific misbehavior occurred (e.g. "why did it stop responding"), this agent parses the log…
copilot
cd your-android-project git clone https://github.com/haidrrrry/compose-kotlin-agent-skills.git .github/skills/compose-kotlin-agent-skills.
aider
Aider reads CONVENTIONS.md, .aider.conf.yml, and files you add to context.