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 skills add gaelic-ghost/socket --skill xcode-debugger-mcp-workflowgit clone --depth 1 https://github.com/gaelic-ghost/socketWrote 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/gaelic-ghost/socket/xcode-debugger-mcp-workflow)<a href="https://agentmods.dev/skills/gaelic-ghost/socket/xcode-debugger-mcp-workflow"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/xcode-debugger-mcp-workflow/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/gaelic-ghost/socket/xcode-debugger-mcp-workflow"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/xcode-debugger-mcp-workflow.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.00070 | $0.01350 |
| Opus 5.5 | $0.00028 | $0.00540 |
| Sonnet 5.5 | $0.00014 | $0.00270 |
| Haiku 4.5 | $0.00007 | $0.00135 |
Grade A, and why
xcode-debugger-mcp-workflow 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 1mo 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Xcode Debugger MCP Workflow
Purpose
Use Xcode's active debugger session through xcrun mcpbridge as the stable agent-facing LLDB route. Treat the standalone xcrun lldb-mcp executable as experimental until it starts successfully on the selected Xcode toolchain and exposes a documented tool contract.
Xcode And LLDB MCP Boundaries
Xcode 27 exposes two distinct MCP paths:
xcrun mcpbridgeis Xcode's STDIO bridge. It connects an external MCP client to a running Xcode process, selecting it withMCP_XCODE_PIDorMCP_XCODE_SESSION_IDwhen needed. It owns Xcode project tools and the active run/debug-session tools. On the locally observed surface,InvokeDebuggerCommandsends a focused LLDB command to that active debugging session.xcrun lldb-mcpis LLDB's standalone STDIO-to-socket bridge. It discovers an LLDB MCP server or launches a separate backgroundlldbprocess when none exists. Its documented surface is one generallldb_commandtool plus debugger and target resources. It does not document a way to select or take ownership of Xcode's active debugging session.
For a running Xcode app, start with mcpbridge, the active session, and the smallest Xcode-provided debugger command. Use standalone lldb-mcp only for a separately owned LLDB workflow after its startup and tool discovery both succeed.
Current Xcode 27 Beta 3 State
On 2026-07-12, the selected Xcode 27.0 Beta 3 toolchain (27A5218g) resolves both mcpbridge and lldb-mcp. mcpbridge --help works and documents STDIO bridge behavior, Xcode PID/session selection, and agent export behavior. lldb-mcp --help fails before startup because dyld cannot resolve @rpath/lib_CompilerSwiftIDEUtils.dylib, even though that library exists elsewhere inside the Xcode bundle.
This is a local Beta 3 packaging observation. Public Xcode release notes announce lldb-mcp, but neither those notes nor the public LLDB documentation identify this dyld failure as a known issue. Do not claim it affects every Xcode installation or beta. Do not work around this with copied libraries, symlinks, modified Xcode bundles, or a persistent loader-path override. Recheck a later Xcode beta or release before claiming standalone lldb-mcp support.
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.
- 1mo ago First seen · 55 lines · 70 tokens per session scan A fc5d571a5d29
xcode-debugger-mcp-workflow is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 70 tokens to every session and 1,350 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
bug-fix
Use when a bug, regression, or unexpected behaviour is reported and the user wants it fixed end to end — "why is X broken", "this stopped working after Y", "fix this crash". Also use when a symptom is known but its cause is not. Not for building new behaviour, and not for a change whose cause is already proven.
bug-investigate
Use when someone wants to know WHY something is broken and has not asked for it to be fixed — "why is this happening", "what's causing this error", "find out what's wrong", "diagnose this before we decide". Also use before committing to a fix, when the cause is unknown and the decision depends on it. Not for fixing …
app-store-optimization
Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns an impression into an install. Use this to audit or optimize an app listing, plan a launch listing, diagnose poor install conversion, or improve store search visibility.
operating-cadence
Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…
flutter-screenshots
Automate App Store & Google Play screenshot generation for Flutter apps. Scans routing and screens, scores high-value marketing screens, generates self-contained mock harness, runs native simulator captures (iPhone 6.9", iPad 13", Android Phone/Tablet), strips alpha channels, and validates exact store resolutions.
flutter-ui
Build Flutter UI from Figma MCP or image input. Scans src for design tokens (colors, sizes, text styles), existing components, and naming conventions before writing a single line of code. Never hard-codes values.