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 skills add xonovex/platform --skill cross-platform-guidegit clone --depth 1 https://github.com/xonovex/platformWrote 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/xonovex/platform/cross-platform-guide)<a href="https://agentmods.dev/skills/xonovex/platform/cross-platform-guide"><img src="https://agentmods.dev/badge/skills/xonovex/platform/cross-platform-guide/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/xonovex/platform/cross-platform-guide"><img src="https://agentmods.dev/badge/skills/xonovex/platform/cross-platform-guide.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.00149 | $0.01538 |
| Opus 5.5 | $0.00060 | $0.00615 |
| Sonnet 5.5 | $0.00030 | $0.00308 |
| Haiku 4.5 | $0.00015 | $0.00154 |
Grade A, and why
cross-platform-guide 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-platform / portability Guidelines
How to make native C/C++ software portable across operating systems and targets by concentrating every OS dependency behind a thin abstraction, porting one backend at a time, and reaching new targets including the web and new input hardware. The renderer architecture itself lives in gpu-rendering-guide (and gpu-rendering-vulkan-guide for one API); build-system mechanics live in cmake-guide; the C dialect's per-platform file-naming in c99-opinionated-guide.
Requirements
- A codebase where OS access can be (or already is) funneled through interfaces, not called inline throughout app/engine code.
- A build system that can select one backend translation unit per target and define per-platform macros.
Essentials
- One interface for all OS calls - A function-pointer struct (or build-selected header) per concern; callers never
#ifdefor call an OS API directly, see references/platform-abstraction-layer.md - Stub, then fill, in interactivity order - Window → input → OS services → audio; the program links against stubs from hour one, see references/porting-strategy.md
- The web is a backend with hard constraints - Cooperative main loop, async I/O, GL ES mapping, 32-bit pointers, see references/web-wasm-builds.md
- Devices are a backend too - Enumerate, probe, poll non-blocking, map by code, behind the input-source interface, see references/input-devices.md
Abstraction and Porting
- No scattered
#ifdef- Platform variance lives in backend translation units, not in portable logic, see references/platform-abstraction-layer.md - Design the interface first - Shape it before any backend so it doesn't bake in one platform's assumptions, see references/platform-abstraction-layer.md
- Toolchain differences are real bugs - Stricter compilers, pointer width, struct padding; fix at the root, see references/porting-strategy.md
- CI per target - A platform not in the build matrix regresses silently on the next portable-code edit, see references/porting-strategy.md
What ships with it
8 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 · 60 lines · 149 tokens per session scan A 266e34918c7b
cross-platform-guide is a skill published in the GitHub repository xonovex/platform (6 stars, last pushed 5d ago), licensed MIT. It adds 149 tokens to every session and 1,538 once invoked, about $0.0006 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-09-08.
Other skills, from other repositories
pixiv-cli-native
Change or validate pixiv-cli Rust ugoira, cgo/FFI, committed static libraries, vendored dependencies, Linux ABI, and native runner evidence. Use when native sources, library hashes, target toolchains, or encoder behavior change; not for routine Go-only or documentation edits.
code-navigation
Use when navigating or changing Swift, Objective-C, C or C++ code — finding where a symbol is defined, who calls it, what implements a protocol, what a change would break, what a package or type exposes, or what changed between revisions. Says when to ask the sextant MCP server instead of running Grep, Glob or reading…
cpp-pro
Write idiomatic C++ code with modern features, RAII, smart pointers, and STL algorithms. Handles templates, move semantics, and performance optimization. Use PROACTIVELY for C++ refactoring, memory safety, or complex C++ patterns.
c-pro
Write efficient C code with proper memory management, pointer arithmetic, and system calls. Handles embedded systems, kernel modules, and performance-critical code. Use PROACTIVELY for C optimization, memory issues, or system programming.
static-rust
Use for Soma built-in Rust actions, scaffold intent collection, MCP elicitation flows, and CLI/REST action reference.
windows-automation
Best-in-class Windows automation using Python (UI Automation) and AutoHotkey.