Borrowing it
Nothing to install: this file belongs to DebugSwift/XcodeBazelMCP. 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/DebugSwift/XcodeBazelMCP/main/.agents/skills/example-project/SKILL.mdgit clone --depth 1 https://github.com/DebugSwift/XcodeBazelMCPWrote 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/debugswift/xcodebazelmcp/example-project)<a href="https://agentmods.dev/skills/debugswift/xcodebazelmcp/example-project"><img src="https://agentmods.dev/badge/skills/debugswift/xcodebazelmcp/example-project/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/debugswift/xcodebazelmcp/example-project"><img src="https://agentmods.dev/badge/skills/debugswift/xcodebazelmcp/example-project.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00049 | $0.01171 |
| Opus 5.5 | $0.00020 | $0.00468 |
| Sonnet 5.5 | $0.00010 | $0.00234 |
| Haiku 4.5 | $0.00005 | $0.00117 |
Grade A, and why
example-project 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BazelApp Example Project
Location: example_projects/BazelApp/
Quick Reference
| Target | Label | Type | Platform |
|---|---|---|---|
| iOS app | //app:app |
ios_application |
iPhone + iPad |
| macOS app | //mac:mac |
macos_application |
macOS 14+ |
| API tests | //modules/API:APITests |
ios_unit_test |
Simulator |
| Models tests | //modules/Models:ModelsTests |
ios_unit_test |
Simulator |
| macOS tests | //mac:MacTests |
macos_unit_test |
macOS |
App Identity
Defined in tools/shared.bzl:
- Bundle ID:
com.example.SwiftUIApp - Bundle Name:
SwiftUIApp - Minimum iOS: 18.0
- macOS Bundle ID:
com.example.SwiftUIMacApp - Minimum macOS: 14.0
XcodeBazelMCP Config
example_projects/BazelApp/.xcodebazelmcp/config.yaml defines profiles:
| Profile | Target | Platform | Build Mode |
|---|---|---|---|
app |
//app:app |
simulator | debug |
mac |
//mac:mac |
macos | debug |
models |
//modules/Models:ModelsLib |
simulator | none |
mac-tests |
//mac:MacTests |
macos | debug |
Testing Workflows
Simulator (iOS)
bazel_ios_build_and_run target=//app:app
bazel_ios_test target=//modules/API:APITests
bazel_ios_test target=//modules/Models:ModelsTests
Device (physical iPhone/iPad)
bazel_ios_device_build_and_run target=//app:app deviceName=iPad
bazel_ios_device_test target=//modules/API:APITests deviceId=<UDID>
Device builds use --ios_multi_cpus=arm64. The families field in the iOS target includes both iphone and ipad.
macOS
bazel_macos_build target=//mac:mac
bazel_macos_test target=//mac:MacTests
bazel_macos_run target=//mac:mac
Setting Workspace
Before running any build/test tool, set the workspace:
bazel_ios_set_workspace workspacePath=<absolute_path>/example_projects/BazelApp
Or use the CLI:
xcodebazelmcp mcp --workspace <path>/example_projects/BazelApp
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 · 126 lines · 49 tokens per session scan A 0a4a40e4f7f9
example-project is a skill published in the GitHub repository DebugSwift/XcodeBazelMCP (8 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 1,171 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-31.
Other skills, from other repositories
mobiloop-mobile-qa
Test mobile apps with MobiLoop MCP, collect device evidence, and fix and retest confirmed failures within the user's scope. Use for Flutter, React Native, Android, or iOS QA on an emulator, simulator, or device, including relevant mobile security checks.
xcforge
Complete reference for xcforge — 104 MCP tools (114 with the diagnose group) + 113 CLI commands for iOS development. Covers build, test, simulator, physical devices, SPM, UI automation, screenshots, logs, git, visual regression, accessibility, localization, session profiles, diagnosis workflows, plan execution, LLDB…
mobile-automation
Control Android and iOS devices, emulators and simulators — launch apps, tap, swipe, type, take screenshots, read the accessibility tree. Use when a task involves a mobile device or app, mobile UI testing, or reproducing a bug on a phone.
baguette
Drive and inspect iOS simulators with the baguette CLI: taps, swipes, buttons, typing, screenshots, the accessibility tree, logs, and the conditions an app runs under (location, network, appearance, push, UserDefaults), without opening Xcode. Use when an agent must act on or verify a running simulator — a UI flow…
argent-qa-e2e
Write repeatable QA regression e2e tests from test cases, tickets, or acceptance criteria. Use when the user asks to write, automate, or generate an e2e test or preserve an automated regression scenario, with deterministic setup, stable targets, executable structural or visual evidence, and two consecutive full…
verify-ui-change-in-cloud
Verifies user-facing Warp client changes by spawning a cloud agent with computer use to test Warp. Use only when the user explicitly requested computer-use verification or accepted an offer to run it, and ONLY in non-sandboxed environments and local environments. Triggers a cloud agent that runs the test-warp-ui skill.