errors

A rule for handling code errors: fix them only when they appear in responses from the XcodeBuildMCP server tool.

In plain words
What is it for?
Controlling which reported errors may be changed during XcodeBuildMCP development work.
Why use it?
It prevents unrelated or unverified error fixes based on other messages or assumptions.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/getsentry/xcodebuildmcp/errors
Clone the repo
git clone --depth 1 https://github.com/getsentry/XcodeBuildMCP

Made for: Cursor.

Per session 32 This file is loaded in full into every session.
When invoked 32 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00032 $0.00032
Opus 5 $0.00016 $0.00016
Sonnet 5 $0.00006 $0.00006
Haiku 4.5 $0.00003 $0.00003

Measured 2d ago against content hash 1dd0374930e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

errors 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

  • errors — 100% identical, 0 lines differ
  • errors — 100% identical, 0 lines differ
example_projects/iOS/.cursor/rules/errors.mdc · 6 lines

What it actually says

Please don't fix any code errors unless reported by XcodeBuildMCP server tool responses.

Changes

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.

  1. 2d ago First seen · 6 lines · 32 tokens per session scan A 1dd0374930e9

Subscribe to this mod's changes

errors is a cursor rule published in the GitHub repository getsentry/XcodeBuildMCP (6,316 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session, 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.