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-color-outputgit 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-color-output)<a href="https://agentmods.dev/skills/xmake-io/xmake-skills/xmake-color-output"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-color-output/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-color-output"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-color-output.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.00079 | $0.01465 |
| Opus 5 | $0.00039 | $0.00732 |
| Sonnet 5 | $0.00016 | $0.00293 |
| Haiku 4.5 | $0.00008 | $0.00146 |
Grade A, and why
xmake-color-output 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 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.
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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cprint, Color Tags & Disabling Color
cprint / cprintf are xmake's colored terminal printers. They look like print/printf but accept inline style tags:
cprint("${bright green}hello ${clear}xmake")
Available in any script-domain code: on_load, on_build, after_build, on_run, on_test, task bodies, external modules imported via import(). Not available in the description domain (top-level set_*/add_*) — use print there instead, and only for debugging.
Basic usage
cprint("hello") -- plain text, like print
cprint("${red}error") -- red text
cprint("${bright red}ERROR") -- bold red
cprintf("%d errors\n", n) -- printf-style
print("hello, %s", name) -- plain print; no tags, no newline-less variant
Formatting uses string.format-style substitution. cprint adds a trailing newline; cprintf does not.
Tag syntax
Styles are wrapped in ${...} and apply to the rest of the line (or until ${clear}):
cprint("${red}hello ${clear}xmake") -- only "hello " is red
cprint("${bright red underline onyellow}ALERT${clear}")
Multiple attributes are space-separated inside one ${...}.
Complete attribute list
Attributes:
| Tag | Effect |
|---|---|
reset / clear / default |
reset all style |
bright |
bold / highlight |
dim |
dark / faint |
underline |
underline |
blink |
blinking text |
reverse |
swap fg/bg |
hidden |
invisible text |
Foreground colors:
black red green yellow blue magenta cyan white
Background colors (prefix on):
onblack onred ongreen onyellow onblue onmagenta oncyan onwhite
Example:
cprint("${bright red underline onyellow}hello${clear}")
cprint("${dim cyan}note:${clear} did you mean ${bright yellow}--foo${clear}?")
24-bit true color
Since v2.1.7, if the terminal reports truecolor support xmake accepts RGB triples:
import("core.base.colors")
if colors.truecolor() then
cprint("${255;0;0}red") -- foreground RGB
cprint("${on;255;0;0}bg red${clear}") -- background RGB
cprint("${bright 255;0;0 underline}bold red underlined")
cprint("${on;255;0;0 0;255;0}green-on-red${clear}")
end
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 · 172 lines · 79 tokens per session scan A 93192dca08fd
xmake-color-output is a skill published in the GitHub repository xmake-io/xmake-skills (24 stars, last pushed 19d ago), licensed Apache-2.0. It adds 79 tokens to every session and 1,465 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
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…