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-feature-checkgit 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-feature-check)<a href="https://agentmods.dev/skills/xmake-io/xmake-skills/xmake-feature-check"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-feature-check/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-feature-check"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-feature-check.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.00104 | $0.02120 |
| Opus 5 | $0.00052 | $0.01060 |
| Sonnet 5 | $0.00021 | $0.00424 |
| Haiku 4.5 | $0.00010 | $0.00212 |
Grade A, and why
xmake-feature-check 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature & Capability Checks
Xmake can probe the target toolchain at configure time for:
- Does a compiler flag work? (
check_cflags,check_cxxflags) - Does a C/C++ function exist? (
has_cfuncs,has_cxxfuncs) - Does a type exist? (
has_ctypes,has_cxxtypes) - Does an include exist? (
has_cincludes,has_cxxincludes) - Does an arbitrary snippet compile? (
check_csnippets,check_cxxsnippets) - How big / how aligned is a type? (
check_sizeof,check_alignof) - Does a C++ feature work? (
has_features("cxx_constexpr"), …) - Is a tool/program on
PATH? (find_tool,find_program) - Is a library findable? (
find_package)
Use these to branch configuration on capability instead of hard-coding if is_plat(...).
In an option (the declarative form)
Options have a short-hand for capability probes — if the probe succeeds, the option is automatically enabled.
option("has_avx2")
add_cxflags("-mavx2")
add_cxxincludes("immintrin.h")
add_cxxsnippets("int f(){ return _mm256_set1_epi32(1)[0]; }")
option_end()
target("app")
if has_config("has_avx2") then
add_cxflags("-mavx2")
add_defines("HAVE_AVX2=1")
end
At configure time xmake compiles the snippet with -mavx2 and the header — the option becomes true if the whole probe succeeds, false otherwise. Transparently handles cross-compile, different compilers, and cached results.
Short-hands available in option():
| API | Probes |
|---|---|
add_cincludes("x.h") |
#include <x.h> compiles |
add_cxxincludes("x.hpp") |
C++ header is usable |
add_ctypes("ssize_t") |
type exists |
add_cxxtypes("std::filesystem::path") |
C++ type exists |
add_cfuncs("pthread_create") |
function is linkable |
add_cxxfuncs("std::thread") |
C++ function/class is usable |
add_csnippets("snippet code") |
arbitrary C snippet compiles |
add_cxxsnippets("snippet code") |
arbitrary C++ snippet compiles |
add_cflags / add_cxflags |
flag probe |
add_features("c_static_assert") |
named compiler feature |
add_links("foo") |
library links |
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 · 213 lines · 104 tokens per session scan A b243cf84dbad
xmake-feature-check is a skill published in the GitHub repository xmake-io/xmake-skills (24 stars, last pushed 18d ago), licensed Apache-2.0. It adds 104 tokens to every session and 2,120 once invoked, about $0.0005 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.