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/mcp-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/mcp-test)<a href="https://agentmods.dev/skills/blueeventhorizon/swift-selena/mcp-test"><img src="https://agentmods.dev/badge/skills/blueeventhorizon/swift-selena/mcp-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/mcp-test"><img src="https://agentmods.dev/badge/skills/blueeventhorizon/swift-selena/mcp-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.00071 | $0.01003 |
| Opus 5 | $0.00036 | $0.00502 |
| Sonnet 5 | $0.00014 | $0.00201 |
| Haiku 4.5 | $0.00007 | $0.00100 |
Grade A, and why
mcp-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 12d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Test
Swift-Selena MCP サーバーに接続し、全ツールの動作を自動検証する。
前提条件
swift-selena-debugMCP サーバーが Claude Code の MCP 設定に登録済みであること- MCP ツール
mcp__swift-selena-debug__*が利用可能であること
ワークフロー
Step 1: Debug ビルド
swift build
ビルド失敗 → エラーを報告して終了。
Step 2: プロジェクト初期化
mcp__swift-selena-debug__initialize_project
project_path: <プロジェクトルートの絶対パス>
確認ポイント:
- "Project initialized" メッセージが返ること
- LSP 接続状態（available / unavailable）を記録
Step 3: ツール一覧取得
mcp__swift-selena-debug__list_available_tools
返されたツール一覧を記録し、Step 4 のテスト対象とする。
Step 4: 全ツールのテスト実行
各ツールを適切なパラメータで実行する。並列実行可能なものは並列で呼び出す。
テストケース定義
| ツール | テストパラメータ | 成功判定 |
|---|---|---|
find_files |
pattern: "*.swift" |
1件以上のファイルが返る |
search_code |
pattern: "import", include_patterns: ["**/*.swift"] |
マッチが返る（DES-104 §5.1 / REQ-005 の include_patterns 検証を兼ねる） |
search_files_without_pattern |
pattern: "ToolProtocol", include_patterns: ["**/*.swift"] |
パターン不含ファイルが返る（issue #34 の include_patterns 検証を兼ねる） |
list_symbols |
file_path: Sources/ 配下の任意の .swift ファイル |
シンボル一覧が返る |
find_symbol_definition |
symbol_name: プロジェクト内の既知の型名 |
定義箇所が返る |
list_property_wrappers |
file_path: Tests/Fixtures/TestSwiftUIView.swift |
@State 等が検出される |
list_protocol_conformances |
file_path: Tests/Fixtures/TestProtocolConformance.swift |
準拠一覧が返る |
list_extensions |
file_path: Tests/Fixtures/TestExtension.swift |
Extension 一覧が返る |
analyze_imports |
file_path: Sources/ 配下の任意ファイル |
import 依存関係が返る |
get_type_hierarchy |
type_name: プロジェクト内の既知の型名 |
型階層が返る |
find_test_cases |
引数なし、またはテストファイルを指定 | テストケース一覧が返る |
- テストで使うファイルパスは絶対パスで指定すること
- Fixtures ファイルがない場合は Sources/ 配下のファイルで代替する
- ツールがエラーを返した場合は
get_tool_schemaでパラメータを確認してリトライ
Step 5: 結果サマリー
全ツールのテスト結果をテーブルで報告する:
## MCP テスト結果
| # | ツール | 結果 | 備考 |
|---|--------|------|------|
| 1 | initialize_project | ✅ | LSP: available |
| 2 | find_files | ✅ | 42件検出 |
| ... | ... | ... | ... |
✅ 全N件パス / ❌ N件失敗
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.
- 12d ago First seen · 91 lines · 71 tokens per session scan A 5238cf17e99e
mcp-test is a skill published in the GitHub repository BlueEventHorizon/Swift-Selena (5 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 1,003 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
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".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
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.