Borrowing it
Nothing to install: this file belongs to sumx21t-3310/FloatSoda. 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/sumx21t-3310/FloatSoda/main/.agents/skills/openvr-api-reference/SKILL.mdgit clone --depth 1 https://github.com/sumx21t-3310/FloatSodaWrote 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/sumx21t-3310/floatsoda/openvr-api-reference)<a href="https://agentmods.dev/skills/sumx21t-3310/floatsoda/openvr-api-reference"><img src="https://agentmods.dev/badge/skills/sumx21t-3310/floatsoda/openvr-api-reference.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.00129 | $0.01261 |
| Opus 5 | $0.00064 | $0.00630 |
| Sonnet 5 | $0.00026 | $0.00252 |
| Haiku 4.5 | $0.00013 | $0.00126 |
Grade A, and why
openvr-api-reference 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 3d 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.
What it actually says
OpenVR APIリファレンス & 実装必要性評価
src/FloatSoda.OVR/openvr_api.cs はOpenVR SDKのC#生バインディング(P/Invoke)。
このスキルは、そこにあるインターフェースについて聞かれたときに (1) 網羅的な機能リスト と
(2) FloatSodaでの実装必要性評価 の2部構成で答えるための手順。
手順
1. 対象インターフェースの特定
質問文からOpenVRのインターフェース名(例: IVRHeadsetView, IVRApplications, IVRSystem, IVROverlay)
または通称(例: 「ヘッドセットビュー」「アプリケーション登録API」)を特定する。曖昧なら
Grep で openvr_api.cs 内を検索して候補を絞る。
2. 生バインディングを読む
対象の以下3点を openvr_api.cs から読む:
IVRxxxstruct — 関数テーブル定義(delegateの並び順がAPIの全メソッド一覧)CVRxxxclass — 上記を薄くラップした公開クラス(引数名・戻り値はこちらの方が読みやすい)- 関連する
enum/const/VREvent_*(同じ機能領域の定数や、モード値、イベント)
Grep -n "<InterfaceName>" で一括検索すると both struct/class/関連定数がまとめて拾える。
3. 網羅リストを作る
全メソッドを1つも省略せず表形式で出す(このAPIの「一覧化」が目的の質問なので、代表例だけ 挙げて終わるのは不可)。各行:
| # | メソッド | シグネチャ | 機能(日本語で一言) |
signatureが取得系(Get*)とセット系(Set*)で対になっている場合は隣接させる。
setterが無い読み取り専用値(例: AspectRatio)は「setterなし」と明記する。
表の後に、関連定数・関連enum・関連VREventを箇条書きで補足する。
4. 実装必要性を評価する
以下の観点で評価し、2〜4行程度の推奨(結論→理由)としてまとめる。網羅リストとは別に 明確なセクションとして分ける。
- FloatSodaの本流(オーバーレイUI描画)と関係があるか:
DashboardOverlay/WorldSpaceOverlay/DeviceTrackedOverlayの生成・描画・入力に関わる機能か、それとも SteamVR側の周辺システム設定(マニフェスト登録、デスクトップミラー、チャペロン設定など)か。 後者は優先度が低い。 - 3ペルソナに刺さるか([floatsoda-target-users.md]のメモリ参照。VRChatterのvibe-coding用途 / Booth創作者のUnity的発想 / uGUI回避エンジニアのコードオンリー志向)。どのペルソナも 触らなそうな機能(配信者向けミラー設定、開発者専用デバッグAPI等)は必要性が低いと判断する。
- 既存のラップ方針との整合性:
src/FloatSoda.OVR/に既にある型(OVRApplication.csなど) と役割が近ければ「同じノリで機械的にラップを広げる」選択肢もあることを触れる。ブランチ名 (例:143-ovr-applications-launch-control)が示す現在の作業スコープと関係があるかも確認する。 - AGENTS.mdの原則: 状態を増やす場合、コードで表現できない外部ファイル/設定に依存しないか (uGUI回避エンジニア向けの価値提案)。
5. 出力形式
- 見出し「## 機能一覧」+ 表 + 補足箇条書き
- 見出し「## 実装必要性」+ 短い推奨文
このスキル自体はコードを変更しない。AGENTS.mdの「デフォルトでは調査・説明のみ、実装はオーナーの 明示的な指示があるまで行わない」方針に従い、評価だけで終える。
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.
- 3d ago Changed 12f152c5e90b
- 7d ago First seen · 68 lines · 129 tokens per session scan A f3ce058525be
openvr-api-reference is a skill published in the GitHub repository sumx21t-3310/FloatSoda (11 stars, last pushed 2d ago), licensed MIT. It adds 129 tokens to every session and 1,261 once invoked, about $0.0006 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-30.
Other skills, from other repositories
worker-services
Build long-running .NET background services with BackgroundService, Generic Host, graceful shutdown, configuration, logging, and deployment patterns suited to workers and daemons. USE FOR: background services; scheduled workers; hosted services; worker extraction; graceful shutdown, health checks, and service hosting…
aspnet-core
Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET. USE FOR: working on ASP.NET Core apps, services, or middleware; changing auth, routing, configuration, hosting, or deployment behavior; deciding…
minimal-apis
Design and implement Minimal APIs in ASP.NET Core using handler-first endpoints, route groups, filters, and lightweight composition suited to modern .NET services. USE FOR: building new HTTP APIs in ASP.NET Core; creating lightweight microservices; choosing between Minimal APIs and controllers. DO NOT USE FOR…
web-api
Build or maintain controller-based ASP.NET Core APIs when the project needs controller conventions, advanced model binding, validation extensions, OData, JsonPatch, or existing API patterns. USE FOR: working on controller-based APIs in ASP.NET Core; needing controller-specific extensibility or conventions; migrating…
managedcode-communication
Use ManagedCode.Communication when a .NET application needs explicit result objects, structured errors, and predictable service or API boundaries instead of exception-driven control flow. USE FOR: integrating ManagedCode.Communication into services or APIs; replacing exception-driven result handling with explicit…
grpc
Build or review gRPC services and clients in .NET. USE FOR: ASP.NET Core gRPC, protobuf contracts, unary or streaming RPC, gRPC client factory, interceptors, deadlines, cancellation, channel reuse, backend service integration. DO NOT USE FOR: broad browser-facing APIs without gRPC-Web tradeoff review, SignalR realtime…