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/layoutnpx skills add linuxdevel/Avalonia-skills --skill layoutgit 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/layout)<a href="https://agentmods.dev/skills/linuxdevel/avalonia-skills/layout"><img src="https://agentmods.dev/badge/skills/linuxdevel/avalonia-skills/layout.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 | $0.00068 | $0.02757 |
| Opus 5 | $0.00034 | $0.01378 |
| Sonnet 5 | $0.00014 | $0.00551 |
| Haiku 4.5 | $0.00007 | $0.00276 |
Grade A, and why
avalonia-controls-layout 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 3d 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Avalonia Layout Controls
Overview
Layout controls are containers that position and constrain child controls. See avalonia-layout for general sizing/alignment concepts. This skill covers the container control APIs.
Border
Single-child container. Adds background, border, rounded corners, padding, and shadows.
| Property | Type | Notes |
|---|---|---|
Background |
IBrush |
Fill color |
BorderBrush |
IBrush |
Border color |
BorderThickness |
Thickness |
1 or 1,2,1,2 (L,T,R,B) |
CornerRadius |
CornerRadius |
8 or 8,0,8,0 (TL,TR,BR,BL) |
Padding |
Thickness |
Inner spacing |
BoxShadow |
BoxShadows |
Drop shadow(s) |
Child |
Control |
Single child only |
<!-- Card style -->
<Border Background="White"
CornerRadius="8"
BorderBrush="#E0E0E0"
BorderThickness="1"
Padding="16"
BoxShadow="0 2 8 0 #20000000">
<StackPanel Spacing="8">
<TextBlock Text="Card Title" FontWeight="SemiBold" FontSize="16"/>
<TextBlock Text="Card body content goes here." TextWrapping="Wrap"/>
</StackPanel>
</Border>
<!-- Divider line using Border -->
<Border Height="1" Background="#E0E0E0" Margin="0,8"/>
<!-- Multiple box shadows -->
<Border BoxShadow="0 1 3 0 #1A000000, 0 4 6 0 #0D000000" CornerRadius="6" Padding="12">
<TextBlock Text="Elevated card"/>
</Border>
Important:
Borderonly accepts one child. Wrap multiple children in aPanel,StackPanel, orGrid.
ScrollViewer
Adds scrollbars to content that overflows its bounds.
| Property | Type | Notes |
|---|---|---|
HorizontalScrollBarVisibility |
ScrollBarVisibility |
Auto, Visible, Hidden, Disabled |
VerticalScrollBarVisibility |
ScrollBarVisibility |
Auto, Visible, Hidden, Disabled |
Offset |
Vector |
Programmatic scroll position |
Extent |
Size |
Total content size |
Viewport |
Size |
Visible area size |
AllowAutoHide |
bool |
Hides scrollbar when not hovering |
HorizontalSnapPointsType |
SnapPointsType |
Snap behavior |
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.
- 3d ago First seen · 319 lines · 0 tokens per session scan A 8c125915ce69
avalonia-controls-layout is a skill published in the GitHub repository linuxdevel/Avalonia-skills (35 stars, last pushed 4mo ago), licensed MIT. It adds 68 tokens to every session and 2,757 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…