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/linuxdevel/avalonia-skills/preview-servernpx skills add linuxdevel/Avalonia-skills --skill preview-servergit clone --depth 1 https://github.com/linuxdevel/Avalonia-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/linuxdevel/avalonia-skills/preview-server)<a href="https://agentmods.dev/skills/linuxdevel/avalonia-skills/preview-server"><img src="https://agentmods.dev/badge/skills/linuxdevel/avalonia-skills/preview-server.svg" alt="Measured on agentmods" 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.00092 | $0.02829 |
| Opus 5 | $0.00046 | $0.01414 |
| Sonnet 5 | $0.00018 | $0.00566 |
| Haiku 4.5 | $0.00009 | $0.00283 |
Grade A, and why
avalonia-pro-max/preview-server 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 6d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Preview Server — Visual Variant Picker for Avalonia
What this does
Lets the agent show the user 2–3 design alternatives as actual rendered Avalonia screens (not HTML mockups), in a browser-based side-by-side comparison gallery. The user picks one and the agent then builds the chosen design out into the real app.
Why "real Avalonia" matters: HTML mockups misrepresent how Avalonia's Skia renderer, FluentTheme, ControlThemes, acrylic, shadows and font rendering actually look. A user who approves an HTML mockup is often disappointed by the real app. Rendering the actual XAML guarantees fidelity.
When to use
Must use
- User says: "show me some options", "what would this look like", "give me a few designs", "preview", "mockup"
- Building a new screen/window where there are valid stylistic alternatives
- Choosing between theme libraries (Fluent vs Suki vs Semi vs Material)
- Big visual refactor before committing to one direction
Skip
- User has already specified an exact design
- Tiny tweaks to existing UI (just edit it)
- Pure backend / non-visual changes
High-level flow
1. Agent reads requirements (uses brainstorming skill if unclear)
2. Agent generates 3 variant .axaml files in .preview/variants/{1,2,3}/
3. Agent runs render script renders each variant via Avalonia.Headless
→ .preview/output/{variant}/{viewport}-{theme}.png
(e.g. 1/wide-light.png, 1/wide-dark.png,
1/compact-light.png, 1/compact-dark.png)
4. Agent runs serve script starts python http.server, builds index.html
gallery, prints URL: http://localhost:PORT
5. User reviews in browser, replies "I like variant 2"
6. Agent stops the server, copies .preview/variants/2/* into the real project
the chosen variant into the
actual app
The user never has to install anything beyond what's already needed for Avalonia development plus Python (already required by ui-ux-pro-max).
What ships with it
9 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.
- scripts/render_variants.py 6.0 KB runs code
- scripts/scaffold_host.py 8.9 KB runs code
- scripts/serve_gallery.py 11 KB runs code
- templates/example-variant/packages.txt 166 B
- templates/example-variant/PreviewScene.axaml 3.7 KB
- templates/example-variant/README.md 306 B
- templates/example-variant/Resources.axaml 1.9 KB
- templates/example-variant/Styles.axaml 2.1 KB
- templates/README.md 2.1 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.
- 6d ago First seen · 229 lines · 92 tokens per session scan A 4708ac7ef858
avalonia-pro-max/preview-server is a skill published in the GitHub repository linuxdevel/Avalonia-skills (36 stars, last pushed 4mo ago), licensed MIT. It adds 92 tokens to every session and 2,829 once invoked, about $0.0005 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…