Borrowing it
Nothing to install: this file belongs to SoundBlaster/XcodeMCPWrapper. 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/SoundBlaster/XcodeMCPWrapper/main/.agents/skills/mcpbridge-workflow/SKILL.mdgit clone --depth 1 https://github.com/SoundBlaster/XcodeMCPWrapperWrote 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/soundblaster/xcodemcpwrapper/mcpbridge-workflow)<a href="https://agentmods.dev/skills/soundblaster/xcodemcpwrapper/mcpbridge-workflow"><img src="https://agentmods.dev/badge/skills/soundblaster/xcodemcpwrapper/mcpbridge-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/soundblaster/xcodemcpwrapper/mcpbridge-workflow"><img src="https://agentmods.dev/badge/skills/soundblaster/xcodemcpwrapper/mcpbridge-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.00093 | $0.01185 |
| Opus 5.5 | $0.00037 | $0.00474 |
| Sonnet 5.5 | $0.00019 | $0.00237 |
| Haiku 4.5 | $0.00009 | $0.00119 |
Grade A, and why
mcpbridge-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 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mcpbridge-workflow
Task tracking for the mcpbridge-wrapper project development.
Quick Start
Get the next task:
python3 scripts/pick_next_task.py
Mark a task done:
python3 scripts/pick_next_task.py --done P1-T1
Show progress:
python3 scripts/pick_next_task.py --progress
# Or use calc_progress.py for different output formats:
python3 scripts/calc_progress.py --markdown
List all tasks:
python3 scripts/pick_next_task.py --list
Workplan Structure
The workplan at SPECS/Workplan.md contains 66 tasks across 8 phases.
When to read the full workplan:
- Before starting work on a task (to see full acceptance criteria)
- To understand task dependencies in detail
- To review the dependency graph or traceability matrix
For task format details, see references/task-format.md.
| Phase | Focus | Tasks | P0 Tasks |
|---|---|---|---|
| 1 | Foundation & Scaffolding | 6 | 3 |
| 2 | Core Bridge Implementation | 7 | 4 |
| 3 | Response Transformation Engine | 10 | 8 |
| 4 | Edge Case Handling | 9 | 0 |
| 5 | Testing & Verification | 14 | 8 |
| 6 | Packaging & Distribution | 8 | 3 |
| 7 | Documentation | 11 | 3 |
Task IDs follow the pattern P{phase}-T{task} (e.g., P1-T1, P3-T5).
Priority Levels
- P0: Must complete for MVP (critical path)
- P1: Should complete (important but not blocking)
- P2: Nice to have (polish and enhancements)
- P3: Future work (post-MVP)
Scripts
Two scripts are available for task management:
pick_next_task.py
Main task tracker with state persistence.
Location: scripts/pick_next_task.py
calc_progress.py
Calculate and display progress from workplan (no state tracking).
Location: scripts/calc_progress.py
Additional options:
python3 scripts/calc_progress.py --json # JSON output
python3 scripts/calc_progress.py --markdown # Markdown table
python3 scripts/calc_progress.py --todo # Pending tasks only
python3 scripts/calc_progress.py --phase P1 # Phase 1 tasks
What ships with it
2 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.
- 2mo ago First seen · 189 lines · 93 tokens per session scan A e4f7ea137d1c
mcpbridge-workflow is a skill published in the GitHub repository SoundBlaster/XcodeMCPWrapper (20 stars, last pushed 1mo ago), licensed MIT. It adds 93 tokens to every session and 1,185 once invoked, about $0.0004 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-30.
Other skills, from other repositories
omh-research-department
This is a Hermes-native research-department workflow skill.
omh-agent-board
This is a Hermes-native agent-board workflow skill.
company-employee
The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…
bo-process-optimization
A method for examining a business workflow to find waiting, rework, handoff waste, and other delays, then proposing improvements and ways to measure them. It separates observed facts from possible explanations and suggestions.
bo-risk-assessment
A method for assessing operational risks in a process, project, or supplier arrangement using observed facts, possible consequences, and practical response suggestions. It keeps the likelihood of a consequence conditional unless the evidence supports more.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.