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-testsgit 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-tests)<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.
<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>- 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.00048 | $0.00653 |
| Opus 5 | $0.00024 | $0.00327 |
| Sonnet 5 | $0.00010 | $0.00131 |
| Haiku 4.5 | $0.00005 | $0.00065 |
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.
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 passrundir— working directoryrunenvs— environment variables (table)trim_output— trim stdout before comparisonpass_outputs/fail_outputs— substring or list of substrings that decide pass/failgroup— 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.
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 · 97 lines · 48 tokens per session scan A cb44f079b024
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.
Other skills, from other repositories
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.
testing-llm
LLM and AI testing patterns — mock responses, evaluation with DeepEval/RAGAS, structured output validation, and agentic test patterns (generator, healer, planner). Use when testing AI features, validating LLM outputs, or building evaluation pipelines.