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 linuxdevel/Avalonia-skills --skill design-systemgit 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/design-system)<a href="https://agentmods.dev/skills/linuxdevel/avalonia-skills/design-system"><img src="https://agentmods.dev/badge/skills/linuxdevel/avalonia-skills/design-system.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.00055 | $0.03199 |
| Opus 5 | $0.00028 | $0.01599 |
| Sonnet 5 | $0.00011 | $0.00640 |
| Haiku 4.5 | $0.00006 | $0.00320 |
Grade A, and why
avalonia-pro-max/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 8d 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design System for Avalonia
Goal
A design system in Avalonia is a set of named resources (colors, brushes, fonts, doubles, thicknesses) that:
- Live in
ResourceDictionaryfiles merged intoApp.axaml. - Are referenced via
{DynamicResource Name}in views — never hard-coded hex/numbers. - Are split by theme variant (Light/Dark) so the entire UI re-themes instantly.
- Follow a 3-layer naming model: primitive → semantic → component.
3-Layer Token Model
Layer 1 — Primitives (raw values, never used in views)
<!-- Resources/Primitives.axaml -->
<ResourceDictionary xmlns="https://github.com/avaloniaui"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml">
<!-- Color ramp: 50..950 like Tailwind -->
<Color x:Key="Slate50">#F8FAFC</Color>
<Color x:Key="Slate100">#F1F5F9</Color>
<Color x:Key="Slate200">#E2E8F0</Color>
<Color x:Key="Slate500">#64748B</Color>
<Color x:Key="Slate700">#334155</Color>
<Color x:Key="Slate900">#0F172A</Color>
<Color x:Key="Slate950">#020617</Color>
<Color x:Key="Blue500">#3B82F6</Color>
<Color x:Key="Blue600">#2563EB</Color>
<Color x:Key="Blue700">#1D4ED8</Color>
<Color x:Key="Red500">#EF4444</Color>
<Color x:Key="Green500">#22C55E</Color>
<Color x:Key="Amber500">#F59E0B</Color>
</ResourceDictionary>
Layer 2 — Semantic tokens (theme-variant aware)
<!-- Resources/Semantic.axaml -->
<ResourceDictionary xmlns="https://github.com/avaloniaui"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml">
<ResourceDictionary.MergedDictionaries>
<ResourceInclude Source="avares://MyApp/Resources/Primitives.axaml"/>
</ResourceDictionary.MergedDictionaries>
<ResourceDictionary.ThemeDictionaries>
<ResourceDictionary x:Key="Light">
<!-- Surfaces -->
<SolidColorBrush x:Key="SurfaceBackgroundBrush" Color="{StaticResource Slate50}"/>
<SolidColorBrush x:Key="SurfaceBrush" Color="#FFFFFF"/>
<SolidColorBrush x:Key="SurfaceElevatedBrush" Color="#FFFFFF"/>
<SolidColorBrush x:Key="SurfaceMutedBrush" Color="{StaticResource Slate100}"/>
<!-- Text -->
<SolidColorBrush x:Key="TextPrimaryBrush" Color="{StaticResource Slate900}"/>
<SolidColorBrush x:Key="TextSecondaryBrush" Color="{StaticResource Slate700}"/>
<SolidColorBrush x:Key="TextMutedBrush" Color="{StaticResource Slate500}"/>
<SolidColorBrush x:Key="TextOnAccentBrush" Color="#FFFFFF"/>
<!-- Borders / dividers -->
<SolidColorBrush x:Key="BorderBrush" Color="{StaticResource Slate200}"/>
<SolidColorBrush x:Key="BorderStrongBrush" Color="{StaticResource Slate500}"/>
<!-- Brand / status -->
<SolidColorBrush x:Key="AccentBrush" Color="{StaticResource Blue600}"/>
<SolidColorBrush x:Key="DangerBrush" Color="{StaticResource Red500}"/>
<SolidColorBrush x:Key="SuccessBrush" Color="{StaticResource Green500}"/>
<SolidColorBrush x:Key="WarningBrush" Color="{StaticResource Amber500}"/>
</ResourceDictionary>
<ResourceDictionary x:Key="Dark">
<SolidColorBrush x:Key="SurfaceBackgroundBrush" Color="{StaticResource Slate950}"/>
<SolidColorBrush x:Key="SurfaceBrush" Color="{StaticResource Slate900}"/>
<SolidColorBrush x:Key="SurfaceElevatedBrush" Color="#1E293B"/>
<SolidColorBrush x:Key="SurfaceMutedBrush" Color="#1E293B"/>
<SolidColorBrush x:Key="TextPrimaryBrush" Color="{StaticResource Slate50}"/>
<SolidColorBrush x:Key="TextSecondaryBrush" Color="{StaticResource Slate200}"/>
<SolidColorBrush x:Key="TextMutedBrush" Color="{StaticResource Slate500}"/>
<SolidColorBrush x:Key="TextOnAccentBrush" Color="#FFFFFF"/>
<SolidColorBrush x:Key="BorderBrush" Color="#1E293B"/>
<SolidColorBrush x:Key="BorderStrongBrush" Color="{StaticResource Slate700}"/>
<SolidColorBrush x:Key="AccentBrush" Color="{StaticResource Blue500}"/>
<SolidColorBrush x:Key="DangerBrush" Color="#F87171"/>
<SolidColorBrush x:Key="SuccessBrush" Color="#4ADE80"/>
<SolidColorBrush x:Key="WarningBrush" Color="#FBBF24"/>
</ResourceDictionary>
</ResourceDictionary.ThemeDictionaries>
</ResourceDictionary>
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.
- 8d ago First seen · 307 lines · 55 tokens per session scan A a238f29e816b
avalonia-pro-max/design-system is a skill published in the GitHub repository linuxdevel/Avalonia-skills (36 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 3,199 once invoked, about $0.0003 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
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…
ue-component-model
Create or edit the Universal Editor component configuration (component-definition.json, component-models.json, component-filters.json) for AEM Edge Delivery Services blocks. Use this skill whenever the user mentions component models, component definitions, component filters, block configuration for the Universal…