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-repo-testinggit 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-repo-testing)<a href="https://agentmods.dev/skills/xmake-io/xmake-skills/xmake-repo-testing"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-repo-testing/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-repo-testing"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-repo-testing.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.00082 | $0.01697 |
| Opus 5 | $0.00041 | $0.00848 |
| Sonnet 5 | $0.00016 | $0.00339 |
| Haiku 4.5 | $0.00008 | $0.00170 |
Grade A, and why
xmake-repo-testing 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Packages in xmake-repo
xmake-repo is the official package recipe repository. Each recipe is a packages/<a>/<name>/xmake.lua describing how to fetch, build, and install a library. The repo ships a test script at scripts/test.lua that drives a full install + test build of a recipe exactly like CI does.
Always run it from the xmake-repo checkout root.
The core command
xmake l scripts/test.lua -vD --shallow <package>
xmake l— run a Lua script in the xmake environment.-v— verbose (show each sub-command).-D— diagnosis (full tracebacks on failure; essential when debugging a broken recipe).--shallow— only install the package you asked for, not its dependencies. Dependencies are pulled from the remote binary cache instead of rebuilt locally. This is the single most important flag for iterating quickly.<package>— the package name, e.g.fmt,zlib,boost.
Example — test the fmt recipe:
cd xmake-repo
xmake l scripts/test.lua -vD --shallow fmt
Common variations
Version / branch
Append the version to the package name, same syntax as add_requires:
xmake l scripts/test.lua -vD --shallow "fmt 10.2.1"
xmake l scripts/test.lua -vD --shallow "cmake master"
Quote it — the space matters.
Static vs shared
xmake l scripts/test.lua -vD --shallow -k shared fmt
xmake l scripts/test.lua -vD --shallow -k static fmt
Debug / release
xmake l scripts/test.lua -vD --shallow -m debug fmt
xmake l scripts/test.lua -vD --shallow -m release fmt
Platform / arch
xmake l scripts/test.lua -vD --shallow -p linux -a x86_64 fmt
xmake l scripts/test.lua -vD --shallow -p macosx -a arm64 fmt
xmake l scripts/test.lua -vD --shallow -p mingw -a x86_64 --mingw=/opt/llvm-mingw fmt
xmake l scripts/test.lua -vD --shallow -p android -a arm64-v8a --ndk=~/android-ndk-r26 fmt
xmake l scripts/test.lua -vD --shallow -p iphoneos -a arm64 fmt
xmake l scripts/test.lua -vD --shallow -p wasm --toolchain=emcc fmt
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 · 163 lines · 82 tokens per session scan A 63a3f1eeea8d
xmake-repo-testing is a skill published in the GitHub repository xmake-io/xmake-skills (24 stars, last pushed 19d ago), licensed Apache-2.0. It adds 82 tokens to every session and 1,697 once invoked, about $0.0004 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.