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-runtime-boundary-reviewnpx skills add getsentry/XcodeBuildMCP --skill xcodebuildmcp-runtime-boundary-reviewgit 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-runtime-boundary-review)<a href="https://agentmods.dev/skills/getsentry/xcodebuildmcp/xcodebuildmcp-runtime-boundary-review"><img src="https://agentmods.dev/badge/skills/getsentry/xcodebuildmcp/xcodebuildmcp-runtime-boundary-review.svg" alt="Measured on agentmods" 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 | $0.00040 | $0.00332 |
| Opus 5 | $0.00020 | $0.00166 |
| Sonnet 5 | $0.00008 | $0.00066 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade A, and why
xcodebuildmcp-runtime-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 4d 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 Runtime Boundary Review
Review guardrails for runtime routing and invocation boundaries.
Review scope
- Review-only by default.
- Do not edit product code unless the user explicitly requests implementation changes.
Files to inspect
src/runtime/tool-catalog.tssrc/runtime/tool-invoker.tssrc/runtime/types.tssrc/cli/**src/daemon/**manifests/tools/*.yamlmanifests/workflows/*.yamlxcodebuildmcp.com/app/docs/_content/architecture-runtime-boundaries.mdxxcodebuildmcp.com/app/docs/_content/architecture-manifest-visibility.mdx
Guardrails
- MCP, CLI, and daemon paths use shared handlers.
- Stateful CLI tools route through daemon only when
routing.statefulrequires it. - Do not treat daemon as a third manifest availability mode.
- Dynamic Xcode IDE tools keep daemon routing semantics.
- Catalog filtering respects availability, workflow selection, and predicates.
- Runtime failures surface via runtime/rendering status and fragments.
- Avoid silent fallbacks and parallel invocation paths.
Validation
npm test -- src/runtime/__tests__/tool-invoker.test.tsnpm run typechecknpx skill-check .agents/skills/xcodebuildmcp-runtime-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.
- 4d ago First seen · 42 lines · 40 tokens per session scan A 2c29118daea8
xcodebuildmcp-runtime-boundary-review is a skill published in the GitHub repository getsentry/XcodeBuildMCP (6,321 stars, last pushed 2d ago), licensed MIT. It adds 40 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.…
quick-capture
Use this skill to drop a new task into GSD Task Manager from any AI assistant that has the gsd-mcp-server connected.
xmemo-vscode
Use XMemo from VS Code (and forks like Cursor/Windsurf) to recall project context, capture engineering decisions, preserve handoff state, and connect to the hosted XMemo MCP endpoint safely.
chainstack
Work with the Chainstack MCP server to manage blockchain nodes and projects. Use when deploying nodes, migrating to Chainstack from another RPC provider such as QuickNode or Alchemy, checking platform status, searching Chainstack docs, contacting the Chainstack team, or interacting with the Chainstack platform API via…
freshness-check
Model-aware staleness check before asserting how a PoE mechanic/item/system works, plus a scope filter so league/event mechanics don't bleed into the wrong character. Routes to freshnessindex.md + mechanicsindex.md.
mcp2cli
Use mcp2cli to connect to, explore, and execute commands against any MCP (Model Context Protocol) server from the terminal. Covers discovery, tool invocation, resource reading, prompt execution, alias creation, config management, background jobs, authentication, and JSON output pipelines.