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-networkgit 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-network)<a href="https://agentmods.dev/skills/xmake-io/xmake-skills/xmake-network"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-network/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-network"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-network.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 93 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00073 | $0.02286 |
| Opus 5 | $0.00036 | $0.01143 |
| Sonnet 5 | $0.00015 | $0.00457 |
| Haiku 4.5 | $0.00007 | $0.00229 |
Grade A, and why
xmake-network scanned grade A 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
This proxies **everything** xmake downloads — git, curl, wget, HTTP packages. Unset with `xmake g --proxy=`. How it starts
The opening of the file, as written. The whole thing — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Xmake Network & Download Acceleration
When xrepo install, xmake require, or package fetches are slow or fail, xmake gives you several tools in increasing order of power: manual download dir → global proxy → proxy with host allow-list → pac.lua for full rule-based routing and URL mirroring.
All of these are configured with xmake g (global config) — settings persist across all projects on the machine.
1. Quickest win: manual download directory
If you already have the source tarballs (downloaded by hand, from a mirror, or shared across a team), drop them in a directory and point xmake at it:
xmake g --pkg_searchdirs="/download/packages"
Xmake will search this directory before hitting the network. To find out what filename to put there:
xmake require --info zlib
# -> searchnames: zlib-1.2.11.tar.gz
Drop zlib-1.2.11.tar.gz into /download/packages/ and the next install uses it offline.
Good for: CI caches, air-gapped machines, shared team caches on a file server.
2. Global proxy
xmake g --proxy="http://127.0.0.1:7890"
xmake g --proxy="https://host:port"
xmake g --proxy="socks5://127.0.0.1:1086"
This proxies everything xmake downloads — git, curl, wget, HTTP packages. Unset with xmake g --proxy=.
Notes:
- The protocol is passed through to the underlying downloader.
socks5://only works for curl/git —wgetdoes not support socks5, so packages that xmake fetches via wget may fail. Preferhttp://orhttps://proxies for maximum compatibility. xmake g --helplists all network-related flags.
3. Proxy only for specific hosts
Global proxying slows down non-blocked traffic. Scope it down:
xmake g --proxy="http://127.0.0.1:7890" \
--proxy_hosts="github.com,*.githubusercontent.com,gitlab.*,*.xmake.io"
Only matching hosts go through the proxy; everything else goes direct. * is a Lua pattern wildcard (more flexible than shell glob — any Lua pattern works).
Unset with xmake g --proxy_hosts=.
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.
- 9d ago First seen · 230 lines · 73 tokens per session scan A 51e8895b2bc0
xmake-network is a skill published in the GitHub repository xmake-io/xmake-skills (23 stars, last pushed 17d ago), licensed Apache-2.0. It adds 73 tokens to every session and 2,286 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…