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/avalonia-data-bindingnpx skills add linuxdevel/Avalonia-skills --skill avalonia-data-bindinggit 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-data-binding)<a href="https://agentmods.dev/skills/linuxdevel/avalonia-skills/avalonia-data-binding"><img src="https://agentmods.dev/badge/skills/linuxdevel/avalonia-skills/avalonia-data-binding.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.00060 | $0.02351 |
| Opus 5 | $0.00030 | $0.01175 |
| Sonnet 5 | $0.00012 | $0.00470 |
| Haiku 4.5 | $0.00006 | $0.00235 |
Grade A, and why
avalonia-data-binding 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 — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Avalonia Data Binding
Overview
Avalonia 12: compiled bindings are on by default. The root element implicitly has x:CompileBindings="true". Compiled bindings are verified at build time, require x:DataType, and generate no reflection overhead. Reflection bindings remain available per-binding with x:CompileBindings=False.
Binding Modes
| Mode | Direction | Updates |
|---|---|---|
OneWay |
Source → Target | On source change |
TwoWay |
Source ↔ Target | On either change |
OneTime |
Source → Target | Once at bind time |
OneWayToSource |
Target → Source | On target change |
Default |
Per-property default | Typically TwoWay for input controls, OneWay for display |
Basic Binding Syntax
<!-- Compiled binding — requires x:DataType on scope root -->
<Window xmlns:vm="using:MyApp.ViewModels"
x:DataType="vm:MainViewModel">
<TextBox Text="{Binding Name}"/>
<TextBlock Text="{Binding Name, Mode=OneWay}"/>
<TextBlock Text="{Binding Name, StringFormat='Hello, {0}!'}"/>
</Window>
<!-- Opt out per-binding (reflection binding) -->
<TextBox Text="{Binding Name, x:CompileBindings=False}"/>
<!-- Explicit compiled binding syntax (same as default in Avalonia 12) -->
<TextBox Text="{CompiledBinding Name}"/>
Binding Path Syntax
| Syntax | Meaning |
|---|---|
{Binding Name} |
Property on DataContext |
{Binding Address.Street} |
Nested property path |
{Binding [0]} |
Indexer |
{Binding [key]} |
Dictionary indexer |
{Binding .} |
DataContext itself |
{Binding #controlName.Property} |
Named control in same scope |
{Binding $parent.Property} |
Nearest parent control |
{Binding $parent[Window].Property} |
Nearest parent of type Window |
{Binding $parent[1].Property} |
Parent N levels up |
{Binding $self.Property} |
The control itself |
{Binding $root.Property} |
Root of logical tree |
DataContext
Inherits down the logical tree. Child controls automatically receive the parent DataContext unless overridden.
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 · 312 lines · 60 tokens per session scan A 30d3f088e71f
avalonia-data-binding is a skill published in the GitHub repository linuxdevel/Avalonia-skills (36 stars, last pushed 4mo ago), licensed MIT. It adds 60 tokens to every session and 2,351 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
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…