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 skills/getsentry/xcodebuildmcp/xcodebuildmcp-docs-release-reviewnpx skills add getsentry/XcodeBuildMCP --skill xcodebuildmcp-docs-release-reviewgit clone --depth 1 https://github.com/getsentry/XcodeBuildMCPWhat 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.00039 | $0.00332 |
| Opus 5 | $0.00019 | $0.00166 |
| Sonnet 5 | $0.00008 | $0.00066 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade A, and why
xcodebuildmcp-docs-release-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 2d 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 Docs and Release Review
Review guardrails for documentation, generated references, and release flow consistency.
Review scope
- Review-only by default.
- Do not edit product code unless the user explicitly requests implementation changes.
Files to inspect
README.mdCHANGELOG.mdwhen presentscripts/build-website-manifest.mjsscripts/generate-github-release-notes.mjsscripts/release.shpackage.jsonxcodebuildmcp.com/app/docs/_content/**
Guardrails
- CLI examples match generated CLI catalog/commands.
- Docs do not reference unavailable tools or workflows.
- User-facing behavior changes include changelog updates.
- Release notes derive from a valid changelog section.
- README install snippets align with release script tag replacement.
- Website manifest generation preserves expected normalized fields.
- Docs explain runtime/contracts without deprecated patterns.
- Keep docs-only work from introducing product behavior changes.
- CLI command references in changelog entries are reviewed by
xcodebuildmcp-docs-command-review.
Validation
npm run build- Release notes check when touched:
node scripts/generate-github-release-notes.mjs --version <version> --changelog CHANGELOG.md
npx skill-check .agents/skills/xcodebuildmcp-docs-release-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.
- 2d ago First seen · 43 lines · 39 tokens per session scan A 485870906d85
xcodebuildmcp-docs-release-review is a skill published in the GitHub repository getsentry/XcodeBuildMCP (6,321 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 332 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
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…
client-scripts
Write ServiceNow client scripts (onLoad/onChange/onSubmit/onCellEdit) using gform, guser, GlideAjax, field visibility/mandatory toggles, and validation with debounced server calls.
agoragentic-transaction-assurance
Prepare, evaluate, and reconcile autonomous agent transactions without self-granting payment or owner authority. Use when an agent must bind principal authority, seller terms, payment evidence, execution, delivered outcome, and reconciliation; handle paid retries safely; or prepare an authority request for owner…
linkding
Manage bookmarks with Linkding. Use when the user asks to "save a bookmark", "add link", "search bookmarks", "list my bookmarks", "find saved links", "tag a bookmark", "archive bookmark", "check if URL is saved", "list tags", "create bundle", or mentions Linkding bookmark management.
debugging-mutations
Verify what changed on a ServiceNow instance after a tool call — sysaudit inspection, syslog/transaction logs, session context, Flow Designer execution logs, outbound HTTP traces.
maya-shot-export
Pipeline stage — shot-level export: frame ranges, cameras, FBX / Alembic packaging for editorial. Use when packaging shot data for downstream departments. Not for full pipeline publish (maya-pipeline) or scene assembly (maya-scene-assembly).