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/parsernpx skills add eksdev007/xcodeinstrumentmcp --skill parsergit 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.00057 | $0.00308 |
| Opus 5 | $0.00028 | $0.00154 |
| Sonnet 5 | $0.00011 | $0.00062 |
| Haiku 4.5 | $0.00006 | $0.00031 |
Grade A, and why
parser 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
Parser
Use this skill for parser and normalization work.
Goal
Produce deterministic, bounded, versionable normalized outputs from Apple export data without claiming more precision than the source actually supports.
Rules
- Prefer deterministic normalization over clever heuristics.
- Preserve stable keys and stable ordering where the format allows it.
- Keep raw-source ambiguity visible in the normalized model instead of hiding it.
- Do not silently discard data unless the spec explicitly says to.
- Separate parsing from ranking and presentation logic.
- Keep adapter-specific code out of shared domain types where possible.
Required workflow
- Inspect the relevant fixture family before changing parser behavior.
- Update or add fixtures in the same change as the parser edit.
- Update expected normalized outputs and golden summaries if behavior changes.
- Run targeted tests first, then
bash scripts/verify.sh.
Precision policy
- Never fabricate durations, counts, or ownership information.
- When symbols, threads, or intervals are only partially known, model that uncertainty explicitly.
- Prefer lossless capture in the IR and lossy reduction only in later stages.
Done criteria
A parser change is not done until fixtures, expected outputs, and tests reflect the new behavior.
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 · 39 lines · 57 tokens per session scan A 47d2369faaaf
parser is a skill published in the GitHub repository eksdev007/xcodeinstrumentmcp (2 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 308 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".