xmake-rules

xmake-rules is a skill for Claude Code from xmake-io/xmake-skills. It costs 50 tokens per session (1,012 once invoked), scanned A, original, Apache-2.0.

A reference for using Xmake, a build tool for compiling software, with reusable rules for build modes, platforms, libraries, and file-processing steps.

In plain words
What is it for?
Use it when applying Xmake's built-in rules or creating rules for a new file type or code-generation step.
Why use it?
It reduces guesswork when configuring how a project is built, including debug or release builds and generated source files.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the xmake-skills plugin — 58 skills shipped together

Good fit Use it when applying Xmake's built-in rules or creating rules for a new file type or code-generation step.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xmake-io/xmake-skills/xmake-rules
Install

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.

Any agent
npx skills add xmake-io/xmake-skills --skill xmake-rules
Clone the repo
git clone --depth 1 https://github.com/xmake-io/xmake-skills

Made for: Claude Code.

Or install xmake-skills, the plugin that ships this one along with the rest of its 58 skills.

Wrote 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.

agentmods badge for xmake-rules

README.md
[![agentmods](https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-rules/github.svg)](https://agentmods.dev/skills/xmake-io/xmake-skills/xmake-rules)
Your own site
<a href="https://agentmods.dev/skills/xmake-io/xmake-skills/xmake-rules"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-rules/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.

agentmods 80×15 button for xmake-rules

Your own site · 80×15
<a href="https://agentmods.dev/skills/xmake-io/xmake-skills/xmake-rules"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,012 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.01012
Opus 5 $0.00025 $0.00506
Sonnet 5 $0.00010 $0.00202
Haiku 4.5 $0.00005 $0.00101

Measured 11d ago against content hash dc1a55a0fef4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

xmake-rules 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.

skills/project-config/xmake-rules/SKILL.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Xmake Rules

Rules are reusable bundles of build logic. You apply them with add_rules(...) at project or target scope, or define your own with rule(...).

Common built-in rules

Build modes (at project scope):

add_rules("mode.debug", "mode.release", "mode.releasedbg", "mode.minsizerel")

This enables xmake f -m debug|release|... and sets the corresponding flags.

Target-level built-ins:

target("app")
    add_rules("c++.unity_build", {batchsize = 8})   -- unity builds
    add_rules("c.unity_build")
    add_rules("win.sdk.application")                -- Windows GUI entry
    add_rules("qt.widgetapp")                       -- Qt widgets app
    add_rules("xcode.application")                  -- iOS/macOS app bundle
    add_rules("plugin.compile_commands.autoupdate", {outputdir = "."})

plugin.compile_commands.autoupdate automatically regenerates compile_commands.json on every build — great for clangd/LSP.

File-transform rules

These attach to individual files through add_files(..., {rules = ...}):

-- embed a binary file as a c array (foo.bin -> foo.bin.h)
add_files("res/foo.bin", {rules = "utils.bin2c"})

-- embed it as an object file instead, no header generated
add_files("res/foo.bin", {rules = "utils.bin2obj"})

-- patch a source file while building, without touching the file on disk
add_files("src/foo.c", {rules = "utils.replace",
                        replaces = {{"RDKCONST%);", "VDKREG);"}}})
add_files("src/foo.c", {rules = "utils.replace",
                        replaces = {{"RDKCONST);", "VDKREG);"}}, replace_plain = true})
add_files("src/foo.c", {rules = "utils.replace", replaces = function (content)
    return (content:gsub("old", "new"))
end})

The generated header holds only the byte list, and the rule adds its directory to the target's includedirs itself, so the consumer is:

static const unsigned char g_foo[] = {
#include "foo.bin.h"
};

utils.replace (v3.0.9+) is the clean way to carry a small vendor patch: the transform runs in the build directory, the repository stays unmodified. utils.bin2c / utils.bin2obj (v3.1.0 gained lua-file transforms and ppc/mips support) embed resources without a generator step.

Read the full file on GitHub · 113 lines

Changes

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.

  1. 11d ago First seen · 113 lines · 50 tokens per session scan A dc1a55a0fef4

Subscribe to this mod's changes

xmake-rules is a skill published in the GitHub repository xmake-io/xmake-skills (24 stars, last pushed 18d ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,012 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

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…

vercel/next.js · 170 tokens

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…

vercel/next.js · 103 tokens