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-optionsgit 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-options)<a href="https://agentmods.dev/skills/xmake-io/xmake-skills/xmake-options"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-options/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-options"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-options.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.00050 | $0.00524 |
| Opus 5 | $0.00025 | $0.00262 |
| Sonnet 5 | $0.00010 | $0.00105 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
xmake-options 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.
What it actually says
Xmake Options
Options are user-facing switches that can be set via xmake f --name=value and queried from targets and conditions.
Declaring an option
option("enable_foo")
set_default(false)
set_showmenu(true)
set_description("Enable the foo subsystem")
option_end()
set_showmenu(true) makes the option visible in xmake f --menu and xmake f --help.
Using an option from a target
target("app")
add_files("src/*.cpp")
if has_config("enable_foo") then
add_files("src/foo/*.cpp")
add_defines("ENABLE_FOO=1")
end
has_config("name") returns true when the option is truthy. Use get_config("name") to read the actual value.
Enumerated / typed options
option("backend")
set_default("vulkan")
set_values("vulkan", "metal", "d3d12")
set_showmenu(true)
xmake f --backend=metal
Options that probe the host
option("has_avx2")
add_cxflags("-mavx2")
add_cxxincludes("immintrin.h")
add_cxxsnippets("int f(){ return _mm256_set1_epi32(1)[0]; }")
Xmake runs the snippet at configure time; the option becomes enabled if the probe compiles.
Generating a config header
target("app")
set_configdir("$(buildir)/config")
add_configfiles("src/config.h.in")
set_configvar("ENABLE_FOO", has_config("enable_foo") and 1 or 0)
src/config.h.in can reference ${define ENABLE_FOO} or ${ENABLE_FOO}.
Command-line usage
xmake f --enable_foo=y --backend=metal -m release
xmake
When to branch out
- Per-target flags —
xmake-targets - Toolchain selection via options —
xmake-toolchains
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 · 81 lines · 50 tokens per session scan A 04f6782aeeb9
xmake-options is a skill published in the GitHub repository xmake-io/xmake-skills (24 stars, last pushed 17d ago), licensed Apache-2.0. It adds 50 tokens to every session and 524 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…