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 xmake-io/xmake-skills --skill xmake-cudagit clone --depth 1 https://github.com/xmake-io/xmake-skillsWrote 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/xmake-io/xmake-skills/xmake-cuda)<a href="https://agentmods.dev/skills/xmake-io/xmake-skills/xmake-cuda"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-cuda/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/xmake-io/xmake-skills/xmake-cuda"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-cuda.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.01159 |
| Opus 5 | $0.00028 | $0.00580 |
| Sonnet 5 | $0.00011 | $0.00232 |
| Haiku 4.5 | $0.00006 | $0.00116 |
Grade A, and why
xmake-cuda 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 10d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building CUDA with Xmake
Xmake detects CUDA automatically and handles device code + host code compilation, dependency scanning, and device linking.
1. Minimal project
xmake create -P test -l cuda
cd test
xmake
add_rules("mode.debug", "mode.release")
target("test")
set_kind("binary")
add_files("src/*.cu")
2. Target kinds
target("app") set_kind("binary")
target("staticcuda") set_kind("static")
target("sharedcuda") set_kind("shared")
3. SDK / version selection
xmake f --cuda=/usr/local/cuda-12.2 -- specific install
xmake f --cuda=12.2 -- version; looks up default install
xmake f --cuda_sdkver=11.8 -- v3.0.5+, per-project SDK version
xmake f --cuda_sdkver=11.x -- any 11.x
xmake f --cuda_sdkver=auto -- auto-detect (default)
Persist globally:
xmake g --cuda=/usr/local/cuda-12.2
4. GPU architecture
target("app")
add_files("src/*.cu")
add_cugencodes("sm_70", "sm_86", "sm_90") -- compile for these archs
add_cugencodes("native") -- just the host GPU
add_cugencodes takes sm_XX strings or native. Multiple calls accumulate; xmake emits -gencode=arch=compute_XX,code=sm_XX per entry.
5. Device linking
Device-linking is automatic for binary and shared targets:
target("app")
set_kind("binary")
add_files("src/*.cu")
-- device link runs automatically
Disable it (rarely needed):
set_policy("build.cuda.devlink", false)
static targets — manual device link
Static libraries are not device-linked by default. If a downstream binary has no .cu files but depends on a static cuda lib, you'll hit "undefined reference to _device..." errors. Fix by opting in:
target("cudalib")
set_kind("static")
add_files("src/*.cu")
add_values("cuda.build.devlink", true) -- force device link for this static target
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.
- 10d ago First seen · 134 lines · 55 tokens per session scan A 6d86f01b90e2
xmake-cuda is a skill published in the GitHub repository xmake-io/xmake-skills (24 stars, last pushed 17d ago), licensed Apache-2.0. It adds 55 tokens to every session and 1,159 once invoked, about $0.0003 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
zoom-meeting-sdk-unreal
Zoom Meeting SDK for Unreal Engine wrapper integrations. Use when building Unreal projects that embed Zoom meetings with C++ and Blueprint wrappers, including wrapper-to-SDK mapping concerns.
ax-cpp-gen
Use when writing C++ code with axllm for AxGen programs, forward calls, indexed multi-sampling, result pickers, streaming, tools, assertions, traces, usage, and output parsing.
doca-argp
Use this skill for hands-on DOCA Arg Parser CLI work on a shipped sample or new DOCA-using app — adding / removing / renaming flags; wiring docaargpinit → register params → docaargpstart → docaargpdestroy in order; picking a parameter type from the full public enum (DOCAARGPTYPESTRING, INT, BOOLEAN, DEVICE, DEVICEREP…
cpu-kernels
Provides guidance for writing, optimizing, and benchmarking C++ CPU kernels with SIMD intrinsics (AVX2/AVX512) for the Hugging Face kernels ecosystem. Includes a two-phase workflow: Phase 1 correctness (generic → AVX2) and Phase 2 performance exploration (AVX512 with branching trial loop), runtime CPU dispatch, OpenMP…
llvm-learning
Comprehensive learning resources and tutorials for LLVM, Clang, and compiler development. Use this skill when helping users learn LLVM internals, find educational resources, or understand compiler concepts.
llvm-security
Expertise in LLVM security features including sanitizers, hardening techniques, exploit mitigations, and secure compilation. Use this skill when implementing security-focused compiler features, analyzing vulnerabilities, or hardening applications.