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 avalonia-versionsgit 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/avalonia-versions)<a href="https://agentmods.dev/skills/linuxdevel/avalonia-skills/avalonia-versions"><img src="https://agentmods.dev/badge/skills/linuxdevel/avalonia-skills/avalonia-versions/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/linuxdevel/avalonia-skills/avalonia-versions"><img src="https://agentmods.dev/badge/skills/linuxdevel/avalonia-skills/avalonia-versions.svg" alt="Reviewed on agentmods" width="80" 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.03705 |
| Opus 5.5 | $0.00037 | $0.01482 |
| Sonnet 5.5 | $0.00018 | $0.00741 |
| Haiku 4.5 | $0.00009 | $0.00370 |
Grade A, and why
avalonia-versions 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 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.
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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Avalonia Versions & Feature Matrix
Supported Versions
| Line | Latest patch | Released | .NET | Status |
|---|---|---|---|---|
| 12.1 | 12.1.4 | 12.1.0: Jul 2026 | net8.0+ (net10.0 recommended; required for Android/iOS) | Current stable — default for new projects |
| 12.0 | 12.0.5 | 12.0.0: Apr 2026 | same as 12.1 | Supported — drop-in upgrade to 12.1 |
| 11.3 | 11.3.22 | — | netstandard2.0 / net6.0+ / .NET Framework | Legacy — maintenance only; plan migration |
Versions older than 11.3 are out of scope; treat them like 11.3 but expect missing APIs.
Step 1 — Detect the Project's Version
Before writing code, find the version. Search in this order:
Directory.Packages.props→<PackageVersion Include="Avalonia" Version="..."/>*.csproj→<PackageReference Include="Avalonia" Version="..."/>Directory.Build.props→ anAvaloniaVersionproperty or similardotnet list package | grep -i avalonia
grep -rhoE 'Include="Avalonia(\.Desktop)?" Version="[^"]+"' --include='*.csproj' --include='*.props' .
- No project yet → use 12.1.x (latest patch),
net10.0. - Mixed versions across
Avalonia.*packages → bug. All coreAvalonia.*packages must share one version (third-party themes/controls have their own versioning). ReactiveUI.Avalonia,Avalonia.Controls.WebView,Avalonia.Controls.DataGrid,Avalonia.Controls.TreeDataGridversion on their own schedule; check NuGet for the release that matches the core version.
Version Label Convention (used across all skills)
| Label | Meaning |
|---|---|
| (12.0+) | Exists from 12.0.0 onward. Not in 11.x |
| (12.1+) | Exists from 12.1.0 onward. Not in 12.0 or 11.x |
| (11.x) | 11.x API — removed/obsolete in 12. Only use in 11.x projects |
| no label | Works in 11.3, 12.0 and 12.1 |
When a skill shows a 12.x API and an (11.x) alternative side by side, pick the one that matches the project's version. Never mix — e.g. don't use DataObject in a 12.x project.
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 · 184 lines · 92 tokens per session scan A 82c2302f21cf
avalonia-versions is a skill published in the GitHub repository linuxdevel/Avalonia-skills (48 stars, last pushed 10d ago), licensed MIT. It adds 92 tokens to every session and 3,705 once invoked, about $0.0004 per session on Opus 5.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-10-23.
Other skills, from other repositories
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
ci-fixer
CI failures - read error, minimal fix, verify.
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…