xmake-remote-compilation

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

A setup for building, running, and testing a project on one remote server while you edit locally. The server can run Linux, macOS, or Windows.

In plain words
What is it for?
Use it to build on a powerful desktop from a laptop, compile for another operating system, or run software on a machine with a needed GPU, Android toolchain, or Xcode.
Why use it?
It avoids repeated manual SSH commands and lets you use a stronger machine, another operating system, or special hardware without moving your editing workflow.

Skill for Claude Code

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

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/ruki/.xmake/service/server/logs.txt.

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

Good fit Use it to build on a powerful desktop from a laptop, compile for another operating system, or run software on a machine with a needed GPU, Android toolchain, or Xcode.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add xmake-io/xmake-skills
Claude Code
/plugin install 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-remote-compilation

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/xmake-io/xmake-skills/xmake-remote-compilation"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-remote-compilation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,627 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.
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.00072 $0.01627
Opus 5 $0.00036 $0.00813
Sonnet 5 $0.00014 $0.00325
Haiku 4.5 $0.00007 $0.00163

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

Security

Grade A, and why

xmake-remote-compilation 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/performance/xmake-remote-compilation/SKILL.md · 169 lines

How it starts

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

Xmake Remote Compilation

Remote compilation is "run the entire build + run + test on a remote machine, transparently". Different from distributed compilation (which offloads individual compile jobs to a cluster): remote compilation sends one project to one server, and every xmake/xmake run/xmake test command executes there.

Use it for:

  • Editing on a laptop, building on a beefy Linux box.
  • Cross-OS development (compile Windows binaries from macOS or vice versa) without ssh pain.
  • Running targets on a device with the right hardware (GPU/NDK/Xcode).

Compared to ssh-based workflows, this doesn't suffer from flaky terminal sessions and integrates into any editor without IDE-specific remote-dev features.

1. Start the server

xmake service                       # foreground (starts all configured services)
xmake service -vD                   # verbose
xmake service --start               # daemonize
xmake service --stop
xmake service --restart

First run creates ~/.xmake/service/server.conf and prints a token.

Server config

{
    known_hosts = { },
    logfile     = "/home/ruki/.xmake/service/server/logs.txt",
    remote_build = {
        listen  = "0.0.0.0:9691",
        workdir = "/home/ruki/.xmake/service/server/remote_build"
    },
    tokens = { "e438d816c95958667747c318f1532c0f" }
}
  • listen — host:port (default 9691).
  • workdir — where projects are synced on the server.
  • tokens — token allowlist.
  • known_hosts — optional IP allowlist (harden exposed servers).

2. Client config — single host

~/.xmake/service/client.conf:

{
    remote_build = {
        connect = "192.168.56.110:9691",
        token   = "e438d816c95958667747c318f1532c0f"
    }
}

3. Client config — multiple hosts (v3.0.7+)

{
    remote_build = {
        hosts = {
            { name = "local",   connect = "127.0.0.1:9691",     token = "ab9dcb6f..." },
            { name = "windows", connect = "10.5.138.247:9691",  token = "0e052f8c..." },
            { name = "linux",   connect = "10.5.138.100:9691",  token = "7889e254..." }
        }
    }
}

Read the full file on GitHub · 169 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 · 169 lines · 72 tokens per session scan A 92363f44a07f

Subscribe to this mod's changes

xmake-remote-compilation is a skill published in the GitHub repository xmake-io/xmake-skills (23 stars, last pushed 17d ago), licensed Apache-2.0. It adds 72 tokens to every session and 1,627 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.

Related

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…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

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.

open-metadata/OpenMetadata · 37 tokens

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.

emdash-cms/emdash · 43 tokens

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.

emdash-cms/emdash · 48 tokens

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…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens