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 cmake-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/cmake-guide)<a href="https://agentmods.dev/skills/xonovex/platform/cmake-guide"><img src="https://agentmods.dev/badge/skills/xonovex/platform/cmake-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/cmake-guide"><img src="https://agentmods.dev/badge/skills/xonovex/platform/cmake-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.00093 | $0.00614 |
| Opus 5.5 | $0.00037 | $0.00246 |
| Sonnet 5.5 | $0.00019 | $0.00123 |
| Haiku 4.5 | $0.00009 | $0.00061 |
Grade A, and why
cmake-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 7d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CMake Coding Guidelines
Define builds through CMake targets with explicit dependencies, visibility, and installation rules.
Requirements
- CMake ≥ 3.20; modern target-based usage.
Essentials
- Target-based builds - Use targets, no global include/link dirs, see references/target-types.md, references/compile-options.md
- Visibility specifiers - Use PUBLIC/PRIVATE/INTERFACE correctly, see references/visibility-specifiers.md
- Dependencies - Declare explicitly with find_package, see references/find-package.md
- Testing - Enable testing with CTest, see references/testing.md
- Project structure - Organize multi-directory projects, see references/project-structure.md
Gotchas
target_link_librariesscope matters: PRIVATE = consumers don't see it, INTERFACE = no compile, PUBLIC = both. Wrong scope leaks transitive depsfind_packagemay use PATHS or HINTS but ignores both if a config file is on a system path; use<Pkg>_ROOTenv var to force-locate- Generator expressions (
$<CONFIG:Debug>) only evaluate at build time: debugging bymessage()won't show their final values CMAKE_INSTALL_PREFIXis captured at configure time; changing it after first config requires a clean reconfigure
Progressive disclosure
- Read references/target-types.md - Load when choosing between library types or executables
- Read references/visibility-specifiers.md - Load when deciding PUBLIC vs PRIVATE vs INTERFACE
- Read references/compile-options.md - Load when adding compiler flags to targets
- Read references/find-package.md - Load when integrating external dependencies
- Read references/testing.md - Load when setting up CTest or test targets
- Read references/project-structure.md - Load when organizing multi-directory CMake projects
- Read references/generator-expressions.md - Load when using conditional build configuration
- Read references/installation.md - Load when creating install targets or package exports
What ships with it
12 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.
- eval-queries.json 4.7 KB
- evals.json 2.4 KB
- moon.yml 166 B
- references/compile-options.md 250 B
- references/find-package.md 586 B
- references/generator-expressions.md 588 B
- references/installation.md 667 B
- references/project-structure.md 779 B
- references/target-types.md 733 B
- references/testing.md 243 B
- references/visibility-specifiers.md 602 B
- SOURCES.md 758 B
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.
- 7d ago Changed · +2 lines 8daa02ae87bd
- 1mo ago First seen · 37 lines · 93 tokens per session scan A fda082f6babf
cmake-guide is a skill published in the GitHub repository xonovex/platform (6 stars, last pushed 5d ago), licensed MIT. It adds 93 tokens to every session and 614 once invoked, about $0.0004 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.