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-snapshot-fixture-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-snapshot-fixture-review)<a href="https://agentmods.dev/skills/getsentry/xcodebuildmcp/xcodebuildmcp-snapshot-fixture-review"><img src="https://agentmods.dev/badge/skills/getsentry/xcodebuildmcp/xcodebuildmcp-snapshot-fixture-review.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00033 | $0.00398 |
| Opus 5 | $0.00016 | $0.00199 |
| Sonnet 5 | $0.00007 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
xcodebuildmcp-snapshot-fixture-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 8d 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 Snapshot Fixture Review
Review guardrails for fixture and snapshot contract integrity.
Review scope
- Review-only by default.
- Do not edit product code unless the user explicitly requests implementation changes.
Files to inspect
src/snapshot-tests/__fixtures__/**src/snapshot-tests/contracts.tssrc/snapshot-tests/fixture-io.tssrc/snapshot-tests/__tests__/fixture-io.test.tssrc/snapshot-tests/__tests__/json-normalize.test.tssrc/snapshot-tests/__tests__/json-fixture-schema.test.tsxcodebuildmcp.com/app/docs/_content/testing.mdx
Guardrails
- Fixture updates map to intentional behavior changes.
- Do not update fixtures only to make tests pass.
- MCP, CLI, and JSON fixture updates stay aligned.
- JSON fixtures preserve stable structured output envelopes.
- Volatile values are normalized in code, not patched ad hoc in fixtures.
- Missing fixtures are generated through the snapshot update flow.
- Verify project-defined normalization sentinels in normalization code and tests before reporting
them as implausible fixture values. In particular,
99999is an intentional sentinel for volatile UI capture counts. - Group every occurrence of the same root cause into one finding and list the affected fixtures. Do not emit separate findings for equivalent CLI, MCP, text, or JSON drift.
- Do not repeat a finding that is already resolved by the current diff.
Review limits
- Review the changed fixtures and the directly relevant normalization or contract code only.
- Do not run snapshot or smoke suites as part of an automated PR review.
- Prefer one high-confidence cross-fixture finding over multiple speculative discrepancies.
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.
- 8d ago First seen · 45 lines · 33 tokens per session scan A acedab362a98
xcodebuildmcp-snapshot-fixture-review is a skill published in the GitHub repository getsentry/XcodeBuildMCP (6,347 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 398 once invoked, about $0.0002 per session on Opus 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
qa
QA test a live website with Axon discovery/content evidence plus browser automation when interaction is required. Use when the user wants exploratory QA, form testing, navigation/link checks, responsive checks, performance observations, bug reports, or a pre-launch quality review.
code-review
Reviews a supplied code path or diff for correctness, security, maintainability, and style without executing or modifying it.
knowledge-audit
Review and clean up stored memories — find duplicates, contradictions, stale entries, and consolidate.
sumo-qa-implementing-with-tdd
Use after sumo-qa-deciding-approach picks tdd-scaffold, regression-first, or coverage-first-then-refactor — e.g. "write a regression test for this bug" or "scaffold the failing tests first". Walks plan → name-the-risk-and-test-idea → confirm → red → hand off → green → review, one section per turn with confirmation…
blazemeter-performance-testing
Comprehensive guide for BlazeMeter Performance Testing, including load configuration, reporting, JMeter configuration, Taurus, scenarios, and advanced features. Use when working with Performance tests for (1) Configuring load settings and distribution, (2) Creating and running tests (JMeter, Browser, URL/API…
sumo-qa-planning-qa-rollout
Use when you have a chunk of QA work (a story, a PR, a strategy phase) that needs to be turned into a written plan of bite-sized, independently-executable tasks before any test code is written. Walks scope → file structure → bite-sized tasks → confirm, one section per turn. Produces docs/qa/plans/YYYY-MM-DD- .md ready…