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.
git clone --depth 1 https://github.com/getsentry/XcodeBuildMCP-iOS-TemplateWrote 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/rules/getsentry/xcodebuildmcp-ios-template/xcodebuildmcp-tools)<a href="https://agentmods.dev/rules/getsentry/xcodebuildmcp-ios-template/xcodebuildmcp-tools"><img src="https://agentmods.dev/badge/rules/getsentry/xcodebuildmcp-ios-template/xcodebuildmcp-tools/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/rules/getsentry/xcodebuildmcp-ios-template/xcodebuildmcp-tools"><img src="https://agentmods.dev/badge/rules/getsentry/xcodebuildmcp-ios-template/xcodebuildmcp-tools.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.00056 | $0.00910 |
| Opus 5.5 | $0.00022 | $0.00364 |
| Sonnet 5.5 | $0.00011 | $0.00182 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
xcodebuildmcp-tools 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.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
XcodeBuildMCP Tool Usage
To work with this project, build, test, and development commands should use XcodeBuildMCP tools instead of raw command-line calls.
Project Discovery & Setup
// Discover Xcode projects in the workspace
discover_projs({
workspaceRoot: "/path/to/YourApp"
})
// List available schemes
list_schems_ws({
workspacePath: "/path/to/YourApp.xcworkspace"
})
Building for Simulator
// Build for iPhone simulator by name
build_sim_name_ws({
workspacePath: "/path/to/YourApp.xcworkspace",
scheme: "YourApp",
simulatorName: "iPhone 16",
configuration: "Debug"
})
// Build and run in one step
build_run_sim_name_ws({
workspacePath: "/path/to/YourApp.xcworkspace",
scheme: "YourApp",
simulatorName: "iPhone 16"
})
Building for Device
// List connected devices first
list_devices()
// Build for physical device
build_dev_ws({
workspacePath: "/path/to/YourApp.xcworkspace",
scheme: "YourApp",
configuration: "Debug"
})
Testing
// Run tests on simulator
test_sim_name_ws({
workspacePath: "/path/to/YourApp.xcworkspace",
scheme: "YourApp",
simulatorName: "iPhone 16"
})
// Run tests on device
test_device_ws({
workspacePath: "/path/to/YourApp.xcworkspace",
scheme: "YourApp",
deviceId: "DEVICE_UUID_HERE"
})
// Test Swift Package
swift_package_test({
packagePath: "/path/to/YourAppPackage"
})
Simulator Management
// List available simulators
list_sims({
enabled: true
})
// Boot simulator
boot_sim({
simulatorUuid: "SIMULATOR_UUID"
})
// Install app
install_app_sim({
simulatorUuid: "SIMULATOR_UUID",
appPath: "/path/to/YourApp.app"
})
// Launch app
launch_app_sim({
simulatorUuid: "SIMULATOR_UUID",
bundleId: "com.example.YourApp"
})
Device Management
// Install on device
install_app_device({
deviceId: "DEVICE_UUID",
appPath: "/path/to/YourApp.app"
})
// Launch on device
launch_app_device({
deviceId: "DEVICE_UUID",
bundleId: "com.example.YourApp"
})
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 · 191 lines · 56 tokens per session scan A 68c6988d247e
xcodebuildmcp-tools is a cursor rule published in the GitHub repository getsentry/XcodeBuildMCP-iOS-Template (42 stars, last pushed 1y ago), licensed MIT. It adds 56 tokens to every session and 910 once invoked, about $0.0002 per session on Opus 5.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 cursor rules, from other repositories
mobile-testing-patterns
Testing structure and colocated test conventions.
flutter-testing-rules
Specifies testing guidelines for Flutter projects, covering unit, widget, and integration tests.
flutter-testing-rules
Specifies testing guidelines for Flutter projects, covering unit, widget, and integration tests.
android-jetpack-compose---testing-guidelines
Defines testing guidelines for Android Jetpack Compose components, ViewModels, and UseCases.
122-swift-development
122: Swift development workflow including TDD, refactoring, and performance optimization.
android-jetpack-compose---testing-guidelines
Defines testing guidelines for Android Jetpack Compose components, ViewModels, and UseCases.