XcodeBuildMCP is an MCP server and command-line tool that gives coding agents tools for building and working on iOS and macOS projects. It supports workflows involving Xcode and xcodebuild, including project builds and device-related operations. Its catalogue add-ons provide agent instructions and connections for using the MCP server and CLI.
Borrowing it
Nothing to install: this file belongs to getsentry/XcodeBuildMCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/getsentry/XcodeBuildMCP/main/.agents/skills/xcodebuildmcp-test-boundary-review/SKILL.mdgit clone --depth 1 https://github.com/getsentry/XcodeBuildMCPWrote 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/getsentry/xcodebuildmcp/xcodebuildmcp-test-boundary-review)<a href="https://agentmods.dev/skills/getsentry/xcodebuildmcp/xcodebuildmcp-test-boundary-review"><img src="https://agentmods.dev/badge/skills/getsentry/xcodebuildmcp/xcodebuildmcp-test-boundary-review/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/getsentry/xcodebuildmcp/xcodebuildmcp-test-boundary-review"><img src="https://agentmods.dev/badge/skills/getsentry/xcodebuildmcp/xcodebuildmcp-test-boundary-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 41 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00034 | $0.00330 |
| Opus 5.5 | $0.00014 | $0.00132 |
| Sonnet 5.5 | $0.00007 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
xcodebuildmcp-test-boundary-review 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 2mo 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.
What it actually says
XcodeBuildMCP Test Boundary Review
Review guardrails for test isolation, scope, and contract validation.
Review scope
- Review-only by default.
- Do not edit product code unless the user explicitly requests implementation changes.
Files to inspect
src/**/__tests__/**src/test-utils/**src/snapshot-tests/**scripts/**/__tests__/**package.jsonxcodebuildmcp.com/app/docs/_content/testing.mdxxcodebuildmcp.com/app/docs/_content/contributing.mdx
Guardrails
- Unit tests inject command/filesystem/external dependencies.
- Unit tests do not call real
xcodebuild,xcrun, AXe, devices, or simulators. - Prefer testing logic/executor functions over handler wrappers unless testing runtime integration.
- Use existing mock executor helpers.
- Treat snapshot updates as contract changes requiring review.
- Do not add fake e2e/snapshot state to force test success.
- Avoid unsafe TypeScript suppressions.
Validation
- Run targeted Vitest command for touched tests.
npm testnpm run typecheck- If fixtures/schemas changed:
npm run test:snapshotsandnpm run test:schema-fixtures npx skill-check .agents/skills/xcodebuildmcp-test-boundary-review
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.
- 2mo ago First seen · 42 lines · 34 tokens per session scan A 7607971e1b4f
xcodebuildmcp-test-boundary-review is a skill published in the GitHub repository getsentry/XcodeBuildMCP (6,506 stars, last pushed 7d ago), licensed MIT. It adds 34 tokens to every session and 330 once invoked, about $0.0001 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 skills, from other repositories
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
add-test
Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
add-test
Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.
add-test
Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.
add-test
Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.