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-troubleshootinggit 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-troubleshooting)<a href="https://agentmods.dev/skills/xmake-io/xmake-skills/xmake-troubleshooting"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-troubleshooting/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-troubleshooting"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-troubleshooting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00101 | $0.02686 |
| Opus 5 | $0.00051 | $0.01343 |
| Sonnet 5 | $0.00020 | $0.00537 |
| Haiku 4.5 | $0.00010 | $0.00269 |
Grade C, and why
xmake-troubleshooting scanned grade C with 1 finding 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 12d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .xmake # nuclear: drop the whole local cache How it starts
The opening of the file, as written. The whole thing — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Troubleshooting Xmake
When xmake itself (not your project) is misbehaving, work from the cheapest tool to the most invasive: verbose output → profiling env → bisect → debugger.
1. First: verbose and diagnosis output
xmake -v # verbose: show every sub-command
xmake -vD # verbose + diagnosis: full Lua tracebacks on error
xmake f -vD # same but for configure
xmake l -vD path/to/script.lua
-D is the single most important flag when something goes wrong — any Lua error comes back with a full stack into xmake/core/..., which usually tells you exactly which module is unhappy.
Project cache can also mask bugs. If something seems sticky:
xmake f -c # re-run configure, dropping cached state
xmake clean --all
rm -rf .xmake # nuclear: drop the whole local cache
2. Stuck / hang diagnosis (XMAKE_PROFILE=stuck)
Xmake has a built-in stuck-process debugger. Set XMAKE_PROFILE=stuck and it will (a) log every subprocess it spawns and (b) on Ctrl+C print the current Lua stack traceback — so you can see exactly where it was blocked.
Enable it
Linux / macOS:
XMAKE_PROFILE=stuck xmake # one-shot
export XMAKE_PROFILE=stuck && xmake # whole session
Windows PowerShell:
$env:XMAKE_PROFILE="stuck"; xmake
Windows CMD:
set XMAKE_PROFILE=stuck && xmake
Reading the output
Subprocess trace (configure stuck probing a compiler):
$ XMAKE_PROFILE=stuck xmake f -c
<subprocess: sysctl>: /usr/sbin/sysctl -n machdep.cpu.vendor ...
checking for platform ... macosx
<subprocess: which>: which "xcrun -sdk macosx clang"
^C[xmake]: [engine]: stack traceback:
@programdir/core/base/scheduler.lua:429: in function 'base/scheduler.co_suspend'
.../lib/detect/find_program.lua:266: in function ...
@programdir/modules/detect/tools/find_clang.lua:44: ...
This tells you:
- Which subprocess was running when it hung (
which "xcrun -sdk macosx clang"here). - The Lua call stack that led there — e.g.
find_clang→find_program→scheduler.co_suspend, so xmake was waiting on a spawned process that never returned.
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.
- 12d ago First seen · 259 lines · 101 tokens per session scan C a82d9649f86b
xmake-troubleshooting is a skill published in the GitHub repository xmake-io/xmake-skills (24 stars, last pushed 20d ago), licensed Apache-2.0. It adds 101 tokens to every session and 2,686 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.