xmake-tests

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

A guide for declaring and running tests in an Xmake project. Xmake is a build tool for C and C++, and its test support can run programs with chosen arguments, environments, output checks, and test groups.

In plain words
What is it for?
Use it to add tests with xmake.lua, run all or selected cases, group tests, pass arguments or environment variables, and check expected output.
Why use it?
It provides a standard way to connect test cases to build targets and decide whether they pass or fail. It also explains how to use common testing libraries such as GoogleTest, Catch2, and doctest.

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 to add tests with xmake.lua, run all or selected cases, group tests, pass arguments or environment variables, and check expected output.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xmake-io/xmake-skills/xmake-tests
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-tests
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-tests

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/xmake-io/xmake-skills/xmake-tests"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 653 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.00048 $0.00653
Opus 5 $0.00024 $0.00327
Sonnet 5 $0.00010 $0.00131
Haiku 4.5 $0.00005 $0.00065

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

Security

Grade A, and why

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

skills/testing/xmake-tests/SKILL.md · 97 lines

How it starts

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

Xmake Tests

Xmake has built-in test support via add_tests on a target. xmake test builds and runs all declared test cases.

Basic test on an executable

target("app_test")
    set_kind("binary")
    add_files("tests/*.cpp", "src/lib/*.cpp")
    add_tests("default")                                     -- run the binary with no args
    add_tests("with_arg", {runargs = {"--quick"}})
    add_tests("expect_zero", {trim_output = true, pass_outputs = "OK"})
    add_tests("fail_case",  {fail_outputs = {"ERROR", "FATAL"}})

Running:

xmake test                         # run all tests
xmake test app_test/default        # run one case
xmake test -v                      # show output
xmake test -jN                     # parallel

Options per case:

  • runargs — arguments to pass
  • rundir — working directory
  • runenvs — environment variables (table)
  • trim_output — trim stdout before comparison
  • pass_outputs / fail_outputs — substring or list of substrings that decide pass/fail
  • group — tag tests into groups, e.g. group = "unit"xmake test -g unit

Using a test framework

doctest / catch2 (header-only)

add_requires("doctest")

target("unit")
    set_kind("binary")
    add_files("tests/*.cpp")
    add_packages("doctest")
    add_tests("default")

gtest

add_requires("gtest", {configs = {main = true}})

target("unit")
    set_kind("binary")
    add_files("tests/*.cpp", "src/lib/*.cpp")
    add_packages("gtest")
    add_tests("default")

Auto-discovered test targets

A common convention: one test target per file, auto-generated.

for _, file in ipairs(os.files("tests/test_*.cpp")) do
    local name = path.basename(file)
    target(name)
        set_kind("binary")
        set_default(false)                 -- don't build with `xmake`
        add_files(file, "src/lib/*.cpp")
        add_tests("default")
end

set_default(false) keeps test binaries out of the default build; xmake test still picks them up.

Read the full file on GitHub · 97 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. 10d ago First seen · 97 lines · 48 tokens per session scan A cb44f079b024

Subscribe to this mod's changes

xmake-tests is a skill published in the GitHub repository xmake-io/xmake-skills (24 stars, last pushed 17d ago), licensed Apache-2.0. It adds 48 tokens to every session and 653 once invoked, about $0.0002 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.