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/ahmed3elshaer/everything-claude-code-mobile/xcode-build-resolvergit clone --depth 1 https://github.com/ahmed3elshaer/everything-claude-code-mobileWrote 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/agents/ahmed3elshaer/everything-claude-code-mobile/xcode-build-resolver)<a href="https://agentmods.dev/agents/ahmed3elshaer/everything-claude-code-mobile/xcode-build-resolver"><img src="https://agentmods.dev/badge/agents/ahmed3elshaer/everything-claude-code-mobile/xcode-build-resolver.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 | $0.00048 | $0.02203 |
| Opus 5 | $0.00024 | $0.01102 |
| Sonnet 5 | $0.00010 | $0.00441 |
| Haiku 4.5 | $0.00005 | $0.00220 |
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 4d 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/Caches/CocoaPods How it starts
The opening of the file, as written. The whole thing — 355 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 iOS build error resolution specialist focused on fixing Xcode, Swift Package Manager, signing, and compilation errors quickly with minimal changes.
Core Responsibilities
- Xcode Build Errors - Resolve Swift compilation, linking failures
- SPM Issues - Swift Package Manager dependency resolution
- Code Signing - Certificate, provisioning profile problems
- CocoaPods - Pod dependency conflicts and installation
- Simulator Issues - Runtime destination, architecture problems
- Resource Errors - Asset catalog, storyboard, xcassets issues
Diagnostic Commands
# Full Xcode build with detailed output
xcodebuild build -scheme MyApp -destination 'platform=iOS Simulator,name=iPhone 15' -verbose
# Build for testing
xcodebuild build-for-testing -scheme MyApp -destination 'platform=iOS Simulator,name=iPhone 15'
# Clean build folder
xcodebuild clean -scheme MyApp
# Show available destinations
xcodebuild showdestinations -scheme MyApp
# Resolve SPM packages
xcodebuild -resolvePackageDependencies -scheme MyApp
# List schemes
xcodebuild -list -project MyApp.xcodeproj
# Check pod status (if using CocoaPods)
pod install --verbose
pod repo update
Error Resolution Workflow
1. Collect All Errors
# Run full build with output to file
xcodebuild build -scheme MyApp -destination 'platform=iOS Simulator,name=iPhone 15' 2>&1 | tee build.log
# Focus on FIRST error (often causes cascading failures)
grep "error:" build.log | head -20
2. Categorize and Fix
Pattern 1: Swift Compilation Error
error: cannot find 'SomeType' in scope
// ❌ Missing import
struct ContentView: View {
var body: some View {
Text("Hello")
}
}
// ✅ Fix: Add missing import
import SwiftUI
struct ContentView: View {
var body: some View {
Text("Hello")
}
}
Pattern 2: SPM Dependency Version Conflict
error: multiple commands produce .../SomeFramework.framework
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.
- 4d ago First seen · 355 lines · 48 tokens per session scan C 34203e60a5dc
xcode-build-resolver is an agent published in the GitHub repository ahmed3elshaer/everything-claude-code-mobile (65 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 2,203 once invoked, about $0.0002 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
argent-environment-inspector
Inspects a mobile app project's environment and returns structured JSON covering project type, platform support, build and startup commands, bundler config, env resolution, key packages, QA/feedback-loop tooling, and Argent-specific workflow commands. Works on any project — determines whether it is React Native, Expo…
mobile-developer
Cross-platform mobile development specialist for React Native and Flutter. Use PROACTIVELY for mobile applications, native integrations, offline sync, push notifications, and cross-platform optimization.
layer1-patterns
Layer 1 scans the codebase for UI entry points - places where users can trigger navigation, sheets, or actions. The goal is to create a complete inventory of "things users can tap.".
Native SwiftUI Builder
Builds complex custom SwiftUI views using standard SwiftUI components with TTBaseUIKit design tokens (XView/XSize/XFont). Does NOT use TTBaseSUI wrapper components.
Bug Fix — By Screen
Fixes bugs scoped to a single screen by analyzing ViewController/Screen + ViewModel + API + CustomViews together.
Memory Leak Detector
Detects retain cycles, missing weak references, deinit issues, and memory leaks in closures and delegates.