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/acceptance-gatenpx skills add eksdev007/xcodeinstrumentmcp --skill acceptance-gategit 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.00084 | $0.00370 |
| Opus 5 | $0.00042 | $0.00185 |
| Sonnet 5 | $0.00017 | $0.00074 |
| Haiku 4.5 | $0.00008 | $0.00037 |
Grade A, and why
acceptance-gate 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
Acceptance Gate
Use this skill to keep the implementation tied to an objective definition of done.
Goal
Ensure every completion claim is backed by executable checks, fixtures, or explicit manual evidence.
Workflow
- Read the relevant acceptance IDs in
docs/acceptance-matrix.json. - Read the corresponding sections in
docs/launch-checklist-v1.md. - Confirm how the repo currently evaluates those IDs via:
scripts/checklist_status.shscripts/verify.shscripts/release_readiness.sh
- If an acceptance item is not machine-verifiable yet, add the narrowest verification path that matches the repo contract.
- When feature work changes the evidence model, update docs and scripts together.
Rules
- Treat the JSON acceptance matrix as normative for engineering completion.
- Keep acceptance IDs stable once they are referenced by scripts, tests, or reports.
- Prefer deterministic scriptable checks over prose-only status.
- If a check must remain manual, make the evidence path explicit in the checklist.
- Do not let the launch checklist drift from the scripts.
Good outcomes
checklist_status.sh --jsonclearly reflects reality.verify.shcatches the important regressions for current scope.release_readiness.shfails only for real blockers and passes only when the release bar is met.
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 · 38 lines · 84 tokens per session scan A 7a16ea68bc8e
acceptance-gate is a skill published in the GitHub repository eksdev007/xcodeinstrumentmcp (2 stars, last pushed 4mo ago), licensed MIT. It adds 84 tokens to every session and 370 once invoked, about $0.0004 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-compilation-analyzer
Analyze Swift and mixed-language compile hotspots using build timing summaries and Swift frontend diagnostics, then produce a recommend-first source-level optimization plan. Use when a developer reports slow compilation, type-checking warnings, expensive clean-build compile phases, long CompileSwiftSources tasks…
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…