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/w-winter/dot314/xcodebuildmcpnpx skills add w-winter/dot314 --skill xcodebuildmcpgit clone --depth 1 https://github.com/w-winter/dot314What 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.00056 | $0.00216 |
| Opus 5 | $0.00028 | $0.00108 |
| Sonnet 5 | $0.00011 | $0.00043 |
| Haiku 4.5 | $0.00006 | $0.00022 |
Grade A, and why
xcodebuildmcp 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.
What it actually says
xcodebuildmcp
This skill wraps an MCP server behind a local CLI so pi agent can use it without MCP support.
Setup
Run once:
cd {baseDir}
npm install
Usage
Use --output json for agent workflows.
{baseDir}/xcodebuildmcp.sh --help
{baseDir}/xcodebuildmcp.sh --output json <command> [flags]
Regenerating the CLI
If the MCP server adds/removes tools, regenerate the CLI from its embedded metadata:
cd {baseDir}
npx mcporter generate-cli --from ./xcodebuildmcp.ts
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.
- 2d ago First seen · 37 lines · 56 tokens per session scan A 369d2fe94e89
xcodebuildmcp is a skill published in the GitHub repository w-winter/dot314 (125 stars, last pushed 8d ago), licensed MIT. It adds 56 tokens to every session and 216 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-08-30.
Other skills, from other repositories
pi-commandcode-release
Use when preparing, validating, publishing, or documenting a pi-commandcode-provider release/deployment, including version bumps, changelog entries, npm publish, GitHub releases, tags, and release follow-up comments.
orch
PRIMARY AGENT ONLY. Load to orchestrate a Linear or GitHub work item from preparation through merge.
iced-rs
Load whenever building or debugging an Iced UI.
linear
Load for any Linear read or write: issues, projects, cycles, milestones, initiatives, labels.
preflight
Load to run, tune, or debug preflight.
bot-instructions
Load to render, check or adopt a repo's GitHub review-bot instruction files from the shared doctrine plus its bot-instructions.toml, or to read the doctrine, the TOML schema, the render rules and the validators.