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/implementation-loopnpx skills add eksdev007/xcodeinstrumentmcp --skill implementation-loopgit 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.00072 | $0.00539 |
| Opus 5 | $0.00036 | $0.00269 |
| Sonnet 5 | $0.00014 | $0.00108 |
| Haiku 4.5 | $0.00007 | $0.00054 |
Grade A, and why
implementation-loop 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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementation Loop
Use this skill when working through the xcodeinstrumentmcp delivery loop over many changes.
Goal
Move the repository toward a releasable state by selecting the highest-value unfinished work, implementing it in bounded slices, and proving progress with the repo scripts.
Primary workflow
- Read
AGENTS.mdanddocs/task-definition.mdbefore making changes. - Inspect
docs/acceptance-matrix.jsonand identify the highest-priority failing or unimplemented acceptance IDs. - Choose the smallest implementation slice that can move one or more important IDs forward.
- Before coding, inspect the nearby package boundaries and existing docs so the change stays aligned with the repo architecture.
- Implement the slice with minimal, production-oriented changes.
- After each meaningful change, run
bash scripts/verify.sh. - If
verify.shfails, fix the most relevant failure before expanding scope. - Repeat until the selected acceptance IDs are green or until a clearly documented blocker is found.
- Before declaring broad completion, run
bash scripts/release_readiness.sh.
Working rules
- Prefer end-to-end progress over broad speculative scaffolding.
- Prefer one coherent slice over touching every package lightly.
- Keep the package boundaries intact: CLI, MCP, core, parsers, domain, signposts, sqlite, shared.
- Keep outputs deterministic and bounded.
- Keep privacy-sensitive data local by default.
- Do not silently change schemas, file formats, or public command behavior; update fixtures, docs, and tests in the same change.
- Do not mark a checklist item complete without test, fixture, schema, or documented manual evidence.
Prioritization
When multiple items are open, prefer this order unless the prompt says otherwise:
- Core type-safe domain model and normalized schemas
- Deterministic parser/normalizer behavior backed by fixtures
- High-value CLI workflows
- MCP tool surface for the same workflows
- Persistent database and caching behavior
- Signpost scan/plan/apply/revert flows
- Docs, polish, and release wiring
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 · 51 lines · 72 tokens per session scan A 5e850bfe0a94
implementation-loop is a skill published in the GitHub repository eksdev007/xcodeinstrumentmcp (2 stars, last pushed 4mo ago), licensed MIT. It adds 72 tokens to every session and 539 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…