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 accessibilitygit 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/accessibility)<a href="https://agentmods.dev/skills/linuxdevel/avalonia-skills/accessibility"><img src="https://agentmods.dev/badge/skills/linuxdevel/avalonia-skills/accessibility/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/accessibility"><img src="https://agentmods.dev/badge/skills/linuxdevel/avalonia-skills/accessibility.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.00067 | $0.02625 |
| Opus 5.5 | $0.00027 | $0.01050 |
| Sonnet 5.5 | $0.00013 | $0.00525 |
| Haiku 4.5 | $0.00007 | $0.00263 |
Grade A, and why
avalonia-pro-max/accessibility 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility in Avalonia
Avalonia exposes accessibility through:
| API | Purpose |
|---|---|
AutomationProperties.* attached props |
Names, descriptions, roles, item status |
Focusable / IsTabStop / TabIndex |
Keyboard traversal |
Focus pseudoclasses (:focus, :focus-visible, :focus-within) |
Visible focus indication |
KeyBindings, HotKey, KeyGesture |
Shortcuts |
RequestedThemeVariant, platform settings (TopLevel.PlatformSettings (11.x), visual.GetPlatformSettings() (12.0+)) |
High-contrast / dark mode / reduced motion |
AccessKey (_File) |
Mnemonic underline shortcuts |
ToolTip.Tip |
Hover and screen-reader hints |
Targets: WCAG 2.2 AA, plus Windows UI Automation, macOS NSAccessibility, Linux AT-SPI.
Version notes:
- (12.0+) Linux AT-SPI2 accessibility backend (Orca). In 11.x there is no AT-SPI2 backend, so Linux screen-reader support is not available.
- (12.0+) Validation errors are exposed through automation, and
TextBox.PlaceholderTextis accessible to screen readers. - (12.0+)
TopLevel.PlatformSettingsis removed. Usevisual.GetPlatformSettings()(VisualExtensions). In 11.x useTopLevel.GetTopLevel(this)?.PlatformSettings.
AutomationProperties (Required)
<Button Command="{Binding DeleteCommand}"
AutomationProperties.Name="Delete project"
AutomationProperties.HelpText="Permanently removes the current project and all its files">
<PathIcon Data="{StaticResource TrashIconGeometry}"/>
</Button>
Common properties:
| Property | When | Example |
|---|---|---|
AutomationProperties.Name |
Always for icon-only / image-only / unlabeled controls | "Search" |
AutomationProperties.HelpText |
Long-form explanation | "Searches across all projects" |
AutomationProperties.AcceleratorKey |
Display the keyboard shortcut | "Ctrl+K" |
AutomationProperties.AccessibilityView |
Content / Control / Raw — control visibility to AT |
Raw for purely decorative |
AutomationProperties.IsRequiredForForm |
Required form fields | True |
AutomationProperties.LabeledBy |
When a TextBlock labels another control |
{Binding ElementName=EmailLabel} |
AutomationProperties.LiveSetting |
Polite/Assertive live regions | Polite for toasts |
AutomationProperties.ItemStatus |
Dynamic state (e.g., "Saving…") | "3 of 5 selected" |
AutomationProperties.AutomationId |
Stable test id (for UI tests, also used by AT) | "login.submit" |
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 Changed · +11 lines b146c2bc7701
- 2mo ago First seen · 280 lines · 67 tokens per session scan A becb696ab9dc
avalonia-pro-max/accessibility is a skill published in the GitHub repository linuxdevel/Avalonia-skills (48 stars, last pushed 10d ago), licensed MIT. It adds 67 tokens to every session and 2,625 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.