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-cross-compilationgit 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-cross-compilation)<a href="https://agentmods.dev/skills/xmake-io/xmake-skills/xmake-cross-compilation"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-cross-compilation/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-cross-compilation"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-cross-compilation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 213 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00115 | $0.03453 |
| Opus 5 | $0.00057 | $0.01726 |
| Sonnet 5 | $0.00023 | $0.00691 |
| Haiku 4.5 | $0.00012 | $0.00345 |
Grade A, and why
xmake-cross-compilation 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 11d 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 — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross Compilation with Xmake
Cross compilation means producing binaries for a platform that is not the host you are running xmake on. In xmake it boils down to three choices:
- Which platform (
-p/--plat=) you are targeting. - Which toolchain (SDK + cross prefix + cc/cxx/ld/ar) does the work.
- Any extra flags (includes, libs, cflags) needed for the target.
Most of the time, -p <plat> --sdk=<root> is enough — xmake auto-detects the rest. The rest of this skill is the knobs you reach for when auto-detection is not enough.
1. Typical cross-SDK layout
Xmake auto-detects a toolchain SDK that looks like this:
/home/toolchains_sdkdir
├── bin/
│ ├── arm-linux-gnueabihf-gcc
│ ├── arm-linux-gnueabihf-g++
│ ├── arm-linux-gnueabihf-ld
│ ├── arm-linux-gnueabihf-ar
│ └── arm-linux-gnueabihf-strip
├── lib/
│ └── libc.so, libstdc++.so, ...
└── include/
└── stdio.h, ...
The arm-linux-gnueabihf- part is the cross prefix. Give xmake just --sdk=/home/toolchains_sdkdir and it will:
- Find the
bin/dir. - Detect
arm-linux-gnueabihf-as the cross prefix. - Auto-add
-I<sdk>/includeand-L<sdk>/lib.
xmake f -p cross --sdk=/home/toolchains_sdkdir
xmake
-p cross says "generic cross platform". You can also use -p linux for the same toolchain so that is_plat("linux") returns true in xmake.lua.
2. Built-in platforms (no --sdk gymnastics)
These platforms have shortcuts — xmake knows how to find the tools.
Android
xmake f -p android -a arm64-v8a --ndk=~/android-ndk-r26
xmake
Archs: armeabi-v7a, arm64-v8a, x86, x86_64. Persist the NDK path once:
xmake g --ndk=~/android-ndk-r26 # global, remembered across projects
Optional: --ndk_sdkver=21 pins the minimum API level.
iOS / macOS / tvOS / watchOS
xmake f -p iphoneos -a arm64
xmake f -p iphonesimulator -a arm64
xmake f -p macosx -a arm64 # Apple Silicon
xmake f -p appletvos -a arm64
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.
- 11d ago First seen · 344 lines · 115 tokens per session scan A 2e3cf0a9dea9
xmake-cross-compilation is a skill published in the GitHub repository xmake-io/xmake-skills (24 stars, last pushed 18d ago), licensed Apache-2.0. It adds 115 tokens to every session and 3,453 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
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.