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/eksdev007/xcodeinstrumentmcp/mcpnpx skills add eksdev007/xcodeinstrumentmcp --skill mcpgit clone --depth 1 https://github.com/eksdev007/xcodeinstrumentmcpWhat 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.00064 | $0.00283 |
| Opus 5 | $0.00032 | $0.00142 |
| Sonnet 5 | $0.00013 | $0.00057 |
| Haiku 4.5 | $0.00006 | $0.00028 |
Grade A, and why
mcp 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 yesterday.
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
MCP
Use this skill for the public MCP interface.
Goal
Expose high-value workflows that help agents answer the next engineering question without forcing them to consume raw trace plumbing.
Product rules
- Expose workflows, not low-level exports.
- Keep schemas explicit, bounded, and versionable.
- Keep one tool focused on one job.
- Reuse the same core services that power the CLI.
- Favor stable machine-readable output over presentation-oriented text.
Workflow
- Check the spec for the exact tool contract and scope.
- Implement or update the shared core service first when possible.
- Map the MCP surface onto that service with narrow validation.
- Add or update MCP contract tests.
- Update docs/examples for every public surface change.
Guardrails
- Do not expose raw parser internals as public API.
- Do not return unbounded payloads.
- Do not create separate MCP-only business logic if the same behavior belongs in core.
- Keep backward-compatibility in mind once a tool is named in docs.
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.
- yesterday First seen · 36 lines · 64 tokens per session scan A 81d545b1d892
mcp is a skill published in the GitHub repository eksdev007/xcodeinstrumentmcp (2 stars, last pushed 4mo ago), licensed MIT. It adds 64 tokens to every session and 283 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-31.
Other skills, from other repositories
xcode-build-fixer
Apply approved Xcode build optimization changes following best practices, then re-benchmark to verify improvement. Use when a developer has an approved optimization plan from xcode-build-orchestrator, wants to apply specific build fixes, needs help implementing build setting changes, script phase guards, source-level…
xcode-build-orchestrator
Orchestrate Xcode build optimization by benchmarking first, running the specialist analysis skills, prioritizing findings, requesting explicit approval, delegating approved fixes to xcode-build-fixer, and re-benchmarking after changes. Use when a developer wants an end-to-end build optimization workflow, asks to speed…
spm-build-analysis
Analyze Swift Package Manager dependencies, package plugins, module variants, and CI-oriented build overhead that slow Xcode builds. Use when a developer suspects packages, plugins, or dependency graph shape are hurting clean or incremental build performance, mentions SPM slowness, package resolution time, build…
xcode-build-benchmark
Benchmark Xcode clean and incremental builds with repeatable inputs, timing summaries, and timestamped .build-benchmark/ artifacts. Use when a developer wants a baseline, wants to compare before and after changes, asks to measure build performance, mentions build times, build duration, how long builds take, or wants…
xcode-project-analyzer
Audit Xcode project configuration, build settings, scheme behavior, and script phases to find build-time improvements with explicit approval gates. Use when a developer wants project-level build analysis, slow incremental builds, guidance on target dependencies, build settings review, run script phase analysis…
release
Cut a new pymobiledevice3 release — create the GitHub release (which publishes to PyPI) with a curated Highlights section. Use when asked to "release vX.Y.Z", "cut a release", or "publish a new version".