Borrowing it
Nothing to install: this file belongs to BlueEventHorizon/Swift-Selena. 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/BlueEventHorizon/Swift-Selena/main/.claude/skills/xcode-test/SKILL.mdgit clone --depth 1 https://github.com/BlueEventHorizon/Swift-SelenaWrote 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/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/blueeventhorizon/swift-selena/xcode-test"><img src="https://agentmods.dev/badge/skills/blueeventhorizon/swift-selena/xcode-test.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.00072 | $0.00974 |
| Opus 5.5 | $0.00029 | $0.00390 |
| Sonnet 5.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 1mo 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.
- 1mo 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 3mo ago), licensed MIT. It adds 72 tokens to every session and 974 once invoked, about $0.0003 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-31.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.