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 agentmods add skills/xe/agent-plugins/xe-design-systemnpx skills add Xe/agent-plugins --skill xe-design-systemgit clone --depth 1 https://github.com/Xe/agent-pluginsWhat 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 | $0.00000 | $0.00899 |
| Opus 5 | $0.00000 | $0.00449 |
| Sonnet 5 | $0.00000 | $0.00180 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
xe-design-system 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 2d 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.
This is a copy
100% identical to xe-design-system — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Xe Iaso Design System — Skill
When to use
Reach for this system when building anything that should feel like xeiaso.net — a personal technical blog with a conversational voice, warm neutrals, and a cast of sticker characters. Good fits: long-form posts, one-person portfolios, zine-style project pages, fictional-conversation explainers. Bad fits: enterprise dashboards, consumer apps, anything that wants to feel "clean, modern SaaS."
Files
README.md— full context, content fundamentals, visual foundations, iconographycolors_and_type.css— drop-in tokens + primitives; start herefonts/— Podkova (serif, headings), Schibsted Grotesk (sans, body)assets/— Xe orca mascot logo SVG, Graphviz diagramspreview/— small design-system cards (type, color scales, components)
Using it
- Link
colors_and_type.cssinto your HTML. It registers@font-facefor Podkova and Schibsted Grotesk (Iosevka Curly Iaso is only aspirational — falls back toui-monospace). - Use the CSS vars for colors:
--bg-hard / --bg-soft / --bg-0..4for surfaces,--fg-0..4for text, muted accents (--red,--blue, etc.) in light mode and their-brightsiblings in dark. - Typeset with the defaults —
<h1..h6>are already Podkova, body is Schibsted Grotesk. Addtext-wrap: prettyfor headings (already applied top). - For distinctive interactions, let links pick up the invert-on-hover magenta — don't override
a:hover. - For characters talking, use the Conv/chat pattern shown in
preview/chat-conv.html— stacked rows sharing a--bg-softbackground, 64×64 boxy avatar, name link + message.
Do
- Warm cream surfaces (
#f9f5d7) in light, warm charcoal (#1d2021) in dark. - Serif headings (Podkova 600), sans body.
- 1px borders, soft two-step shadows, 6–12px radii.
- Tabler stroke icons (24×24, stroke-width 2, round caps) when icons are needed — usually they aren't.
- Stickers from
stickers.xeiaso.net/sticker/{char}/{mood}when showing characters speak. - Sentence-case headings, first-person conversational voice, dry humor.
What ships with it
27 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/docker-graph.svg 5.1 KB
- assets/gceu23-demo.svg 7.6 KB
- assets/iaso-fonts-depgraph.svg 3.1 KB
- assets/nix-flakes-terraform-graph.svg 16 KB
- assets/xeiaso-logo.svg 11 KB
- assets/xesite-graph.svg 9.7 KB
- colors_and_type.css 6.7 KB
- fonts/Podkova-VariableFont_wght.ttf 159 KB
- fonts/Podkova-VariableFont_wght.woff2 60 KB
- fonts/SchibstedGrotesk-Italic-VariableFont_wght.ttf 178 KB
- fonts/SchibstedGrotesk-Italic-VariableFont_wght.woff2 74 KB
- fonts/SchibstedGrotesk-VariableFont_wght.ttf 173 KB
- fonts/SchibstedGrotesk-VariableFont_wght.woff2 69 KB
- preview/admonitions.html 3.1 KB
- preview/buttons.html 1.6 KB
- preview/chat-conv.html 1.1 KB
- preview/colors-accents.html 1.9 KB
- preview/colors-links.html 1.2 KB
- preview/colors-surfaces.html 2.1 KB
- preview/post-list.html 852 B
- preview/quotes.html 778 B
- preview/spacing-radii-shadow.html 1.5 KB
- preview/sponsor-card.html 1.1 KB
- preview/tags.html 660 B
- preview/type-body.html 1.1 KB
- preview/type-display.html 1.1 KB
- README.md 9.5 KB
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.
- 2d ago First seen · 48 lines · 0 tokens per session scan A 5f297673b6c0
xe-design-system is a skill published in the GitHub repository Xe/agent-plugins (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 899 tokens. A static security scan graded it A with 0 findings. It is 100% identical to xe-design-system, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.