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/warden/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/warden)<a href="https://agentmods.dev/skills/getsentry/xcodebuildmcp/warden"><img src="https://agentmods.dev/badge/skills/getsentry/xcodebuildmcp/warden/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/warden"><img src="https://agentmods.dev/badge/skills/getsentry/xcodebuildmcp/warden.svg" alt="Reviewed on agentmods" width="80" 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.00060 | $0.00609 |
| Opus 5.5 | $0.00024 | $0.00244 |
| Sonnet 5.5 | $0.00012 | $0.00122 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
warden 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Warden to analyze code changes before committing.
References
Read the relevant reference when the task requires deeper detail:
| Document | Read When |
|---|---|
${CLAUDE_SKILL_ROOT}/references/cli-reference.md |
Full option details, per-command flags, examples |
${CLAUDE_SKILL_ROOT}/references/configuration.md |
Editing warden.toml, triggers, patterns, troubleshooting |
${CLAUDE_SKILL_ROOT}/references/config-schema.md |
Exact field names, types, and defaults |
${CLAUDE_SKILL_ROOT}/references/creating-skills.md |
Writing custom skills, remote skills, skill discovery |
Running Warden
# Analyze uncommitted changes (uses warden.toml triggers)
warden
# Run a specific skill
warden --skill <skill-name>
# Analyze specific files
warden src/auth.ts src/database.ts
# Analyze changes from a git ref
warden main..HEAD
warden HEAD~3
# Auto-apply suggested fixes
warden --fix
# Fail on high-severity findings
warden --fail-on high
Set WARDEN_ANTHROPIC_API_KEY or log in via claude login before running.
Pre-Commit Workflow
After making code changes and before committing:
- Run
wardento analyze uncommitted changes - Review the findings
- Fix issues Warden reports (or use
warden --fixto auto-apply) - Commit the changes
Run Warden once to validate work. Do not loop re-running Warden on the same changes.
Reading Output
Severity levels:
high- Must fix before mergemedium- Worth reviewinglow- Minor improvement
Exit codes: 0 = no findings at or above fail threshold. 1 = findings at or above fail threshold.
Verbosity: -v shows real-time findings. -vv shows debug info (tokens, latency). -q shows errors and summary only.
Commands
| Command | Description |
|---|---|
warden |
Run analysis (default) |
warden init |
Initialize warden.toml and GitHub workflow |
warden add [skill] |
Add skill trigger to warden.toml |
warden sync [remote] |
Update cached remote skills |
warden setup-app |
Create GitHub App via manifest flow |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 77 lines · 60 tokens per session scan A f521ff421145
warden is a skill published in the GitHub repository getsentry/XcodeBuildMCP (6,506 stars, last pushed 7d ago), licensed MIT. It adds 60 tokens to every session and 609 once invoked, about $0.0002 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
code-review
Reviews a supplied code path or diff for correctness, security, maintainability, and style without executing or modifying it.
reviewing-update-sets
Reviewing, analyzing, and comparing ServiceNow update sets before promotion, singly or in batches. Shows changes, risks, dependencies, and conflicts. Use when the user mentions update sets, customizations, promotion, code review, change tracking, pre-deployment review, sysupdatexml, customer updates, 'what changed in…
gitlab-review
Review a GitLab merge request, inspect changes and discussions, or prepare and post explicitly requested review feedback. Use for GitLab MRs and review follow-ups, not GitHub pull requests or automatic approval/merge.
pr-reviewer
Review a requested pull request, branch diff or completed task against its actual scope, source and checks. Prepare evidence and comments; post or record a human verdict only when explicitly authorized.
knowledge-audit
Review and clean up stored memories — find duplicates, contradictions, stale entries, and consolidate.
review-guidelines
Additional code review guidelines specific to this codebase. Auto-loaded by the review agent during PR reviews to enforce project conventions.