Companion is a self-hosted, multi-tenant hub for managing personal and organizational SKILL.md libraries used by coding agents. It is for organizations that need to store, validate, version, share, install, update, and synchronize agent skills, with optional named companions that have persistent workspaces and chats. The catalogue skills, agents, and instructions are resources managed or used within this workflow.
Borrowing it
Nothing to install: this file belongs to The-Vibe-Company/companion. 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/The-Vibe-Company/companion/main/.agents/skills/xcodebuildmcp-cli/SKILL.mdgit clone --depth 1 https://github.com/The-Vibe-Company/companionWrote 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/the-vibe-company/companion/xcodebuildmcp-cli)<a href="https://agentmods.dev/skills/the-vibe-company/companion/xcodebuildmcp-cli"><img src="https://agentmods.dev/badge/skills/the-vibe-company/companion/xcodebuildmcp-cli/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/the-vibe-company/companion/xcodebuildmcp-cli"><img src="https://agentmods.dev/badge/skills/the-vibe-company/companion/xcodebuildmcp-cli.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.00055 | $0.00928 |
| Opus 5 | $0.00028 | $0.00464 |
| Sonnet 5 | $0.00011 | $0.00186 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
xcodebuildmcp-cli 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 7d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
XcodeBuildMCP CLI
Use XcodeBuildMCP as the single tool boundary for iOS, macOS, watchOS, tvOS, and visionOS project discovery and verification. It exposes Apple developer-tool workflows through a deterministic CLI and should be used by both Agents and Claude when a task needs a build, test, simulator launch, screenshot, log, debug, or UI inspection.
Protected invariants
- Use the xcodebuildmcp executable for discovery, builds, tests, runs, debugging, logs, and UI automation. Do not fall back to raw xcodebuild, xcrun, or simctl.
- Discover the installed interface from the executable. Do not assume a remembered tool name, workflow, simulator, scheme, or option is current.
- Keep command sequences minimal and observable. Prefer one direct workflow that satisfies the request. For simulator run intent, prefer the combined build-and-run workflow; do not chain build and build-and-run unless the user explicitly asks.
- Check session defaults/configuration before the first build, run, or test action. Use the executable's help to locate the current session-defaults or configuration inspection command.
- Never print, persist, or pass secrets as command arguments. Redact sensitive values from pasted output and screenshots. Keep generated artifacts inside the requested or ignored run area.
- A missing CLI is an environment prerequisite, not permission to install software silently. Tell the user which official installation options are available and ask for authorization before installing or changing the environment.
Help-first discovery
Run these checks in order, stopping once the actual workflow is known:
xcodebuildmcp --help
xcodebuildmcp tools
xcodebuildmcp <workflow> --help
xcodebuildmcp <workflow> <tool> --help
Use the tool list and help output to discover project inspection, session configuration, build, test, simulator, device, log, debug, screenshot, and UI-automation operations. Keep the chosen scheme, project/workspace path, package path, configuration, destination, and test plan explicit when the workflow requires them.
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.
- 7d ago First seen · 82 lines · 55 tokens per session scan A dbae687ed631
xcodebuildmcp-cli is a skill published in the GitHub repository The-Vibe-Company/companion (2,401 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 928 once invoked, about $0.0003 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-09-02.
Other skills, from other repositories
ios-fix
Autonomous iOS bug fixer. (gstack).
google-mobile-ads-validate
Validates a project's Google Mobile Ads (GMA) SDK integration for iOS, Android, or Unity projects. Use when conducting a full pre-launch audit of an app that integrates GMA SDK or when validating any individual GMA SDK integration checks, such as when validating ad unit IDs and ad formats, SKAdNetwork IDs, mediation…
competition-ios-runtime
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for IPA runtime analysis, Frida hooks, Objective-C or Swift method tracing, Keychain inspection, SSL pinning bypass, URL scheme handling, and iOS request-signing recovery. Use when the user asks to hook an IPA, trace Objective-C or Swift…
swiftui-performance-audit
SwiftUI performance: render, scroll, CPU/memory, updates, layout, Instruments.
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
node-connect
Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale…