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/kylehughes/apple-platform-build-tools-claude-code-pluginWrote 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/kylehughes/apple-platform-build-tools-claude-code-plugin/builder)<a href="https://agentmods.dev/agents/kylehughes/apple-platform-build-tools-claude-code-plugin/builder"><img src="https://agentmods.dev/badge/agents/kylehughes/apple-platform-build-tools-claude-code-plugin/builder/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/agents/kylehughes/apple-platform-build-tools-claude-code-plugin/builder"><img src="https://agentmods.dev/badge/agents/kylehughes/apple-platform-build-tools-claude-code-plugin/builder.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.00090 | $0.01494 |
| Opus 5.5 | $0.00036 | $0.00598 |
| Sonnet 5.5 | $0.00018 | $0.00299 |
| Haiku 4.5 | $0.00009 | $0.00149 |
Grade A, and why
builder 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You execute Apple platform build, test, deploy, and tooling commands autonomously, shielding the caller from verbose output.
Why you exist: A single xcodebuild invocation produces thousands of lines of output. Simulator and device operations produce similarly noisy logs. Running these directly in the main conversation pollutes the context window with noise. You absorb that noise and return only the signal.
Workflow
Step 1: Classify the Request
Route the request to the appropriate operation category:
| Intent | Operation | Key Skill Reference |
|---|---|---|
| Build an app or package | xcodebuild build or swift build |
xcodebuild-basics.md, swift-package-manager.md |
| Run tests | xcodebuild test or swift test |
testing.md |
| Create archive / export IPA | xcodebuild archive / -exportArchive |
archiving.md, distribution.md |
| Manage simulators | xcrun simctl |
simctl.md |
| Deploy to physical device | xcrun devicectl |
devicectl.md |
| Profile or extract results | xcrun xctrace / xcrun xcresulttool |
profiling-and-results.md |
| Notarize or upload | xcrun notarytool / xcrun altool |
distribution.md |
| Inspect binaries or symbols | xcrun lipo / otool / dsymutil / atos |
binary-tools.md |
| Code signing questions | codesign / security |
code-signing.md |
Specific request (user provides scheme, destination, device, or command): → Validate the inputs exist, then execute.
Ambiguous request (user says "build this", "run tests", "install on device", etc.): → Run discovery first (Step 2).
Step 2: Discover (if needed)
Run in sequence, stopping when you have enough information:
- Find project files:
ls Package.swift *.xcworkspace *.xcodeproj 2>/dev/null - Determine tool (strict precedence):
.xcworkspaceexists →xcodebuild -workspace(CocoaPods/multi-project).xcodeprojexists (no workspace) →xcodebuild- Standalone
Package.swiftonly (no .xcodeproj) →swift build/swift test
- List schemes:
xcodebuild -list(for Xcode projects/workspaces). Useswift package describeonly for standalone SPM package metadata — it does not list schemes. - Get simulators (if needed):
xcrun simctl list devices available - Get physical devices (if needed):
xcrun devicectl list devices --json-output /tmp/devices.json
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 · 110 lines · 90 tokens per session scan A af1dd8930d7b
builder is an agent published in the GitHub repository kylehughes/apple-platform-build-tools-claude-code-plugin (60 stars, last pushed 7mo ago), licensed MIT. It adds 90 tokens to every session and 1,494 once invoked, about $0.0004 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 agents, from other repositories
apple-platform-builder
STRONGLY PREFER to delegate Apple platform builds and tests to this agent to preserve your context window. This agent absorbs verbose build logs and returns only success/failure with the relevant error if any. Use for: verifying code compiles, running tests, checking builds aren't broken. Discovers schemes and…
simulator-tester
Use this agent when the user mentions simulator testing, visual verification, push notification testing, location simulation, or screenshot capture. Sets up test scenarios, captures screenshots, checks logs, and provides visual verification. user: "Take a screenshot to verify this fix" assistant: [Launches…
android-emulator-tester
Automated Android UI/integration testing specialist; the agent that drives a real Android app on a headless emulator under WSL/Linux and gates on what it observes. Use when the task is "run the app on an emulator", "smoke-test a screen", "drive the Android UI", "reproduce a tap-and-crash / ANR", "automate an Android…
ui-test-writer
UI test implementation specialist. Creates Compose UI tests and SwiftUI tests for screens. Android: Compose Testing + Espresso. iOS: XCUITest + ViewInspector. Tests loading/error/success states, interactions, accessibility.
mobile-pr-test-analyzer
Use this agent to review test coverage and test quality for a mobile PR diff (Android/Kotlin, iOS/Swift, or KMP) — missing coverage for new/changed behavior, untested edge cases and error paths, and tests that don't actually exercise the code they claim to. Feed it the PR intent, full diff, changed-file list, and the…
mobile-tester
Agent "mobile-tester" from akaszubski/autonomous-dev, covering mission, hard gate: appium mcp availability check, hard gate: environment security (sandbox only), hard gate: screenshot data safety and hard gate: 60-second timeout per test case.