Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/blueeventhorizon/swift-selena/xcode-test)<a href="https://agentmods.dev/skills/blueeventhorizon/swift-selena/xcode-test"><img src="https://agentmods.dev/badge/skills/blueeventhorizon/swift-selena/xcode-test.svg" alt="Measured on agentmods" 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.00072 | $0.00974 |
| Opus 5 | $0.00036 | $0.00487 |
| Sonnet 5 | $0.00014 | $0.00195 |
| Haiku 4.5 | $0.00007 | $0.00097 |
Grade A, and why
xcode-test 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 5d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/xcode:test
Xcodeプロジェクトのテストを実行する。
コマンド構文
/xcode:test [scheme-name] [test-target]
| 引数 | 内容 |
|---|---|
| scheme-name | スキーム名（省略時は .xcodeproj から自動検出） |
| test-target | テストターゲット（例: LibraryTests/FooTests。省略時は全テスト） |
Step 1: プラットフォーム判定 [MANDATORY]
以下の順序でプラットフォームを判定する:
- プロジェクト内の
.xcconfigファイルからSDKROOTを検索:
grep -r "^SDKROOT" . --include="*.xcconfig" | head -5
- 見つかった場合、
SDKROOTの値でプラットフォームを決定:
| SDKROOT | プラットフォーム |
|---|---|
iphoneos |
iOS |
macosx |
macOS |
.xcconfigが見つからない場合: AskUserQuestion で iOS / macOS を確認SDKROOTが上記以外の値の場合: AskUserQuestion で確認
Step 2: スキーム・テストターゲット決定
$ARGUMENTS を解析する:
| パターン | スキーム | テストターゲット |
|---|---|---|
| 引数なし | .xcodeproj から自動検出 |
全テスト |
MyApp |
MyApp |
全テスト |
MyApp LibraryTests/FooTests |
MyApp |
LibraryTests/FooTests |
スキーム自動検出:
find . -maxdepth 1 -name "*.xcodeproj" -type d | head -1 | xargs -I{} basename {} .xcodeproj
検出できない場合は AskUserQuestion で確認。
Step 3: テスト環境セットアップ
iOS の場合
シミュレーター検出スクリプトを実行する:
DEVICE_ID=$(${CLAUDE_PLUGIN_ROOT}/skills/test/scripts/resolve_simulator.sh)
- 成功（exit 0）: stdout に UUID が返る →
{DEVICE_ID}として使用 - 失敗（exit 1）: stderr にエラーメッセージと利用可能なデバイス一覧が表示される → AskUserQuestion でデバイスを選択してもらい、手動で UUID を指定
macOS の場合
セットアップ不要。次の Step へ進む。
Step 4: テスト実行
テストスクリプトを実行する。タイムアウトは 600000ms（10分）を設定すること。
macOS
${CLAUDE_PLUGIN_ROOT}/skills/test/scripts/test.sh "{SCHEME}" "platform=macOS"
iOS（テストターゲット指定あり）
${CLAUDE_PLUGIN_ROOT}/skills/test/scripts/test.sh "{SCHEME}" "id={DEVICE_ID}" --sdk iphonesimulator --only-testing "{TEST_TARGET}"
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.
- 5d ago First seen · 117 lines · 72 tokens per session scan A b3ee551574ed
xcode-test is a skill published in the GitHub repository BlueEventHorizon/Swift-Selena (5 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 974 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…