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/layout-patternsnpx skills add linuxdevel/Avalonia-skills --skill layout-patternsgit 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-patterns)<a href="https://agentmods.dev/skills/linuxdevel/avalonia-skills/layout-patterns"><img src="https://agentmods.dev/badge/skills/linuxdevel/avalonia-skills/layout-patterns.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.00066 | $0.02094 |
| Opus 5 | $0.00033 | $0.01047 |
| Sonnet 5 | $0.00013 | $0.00419 |
| Haiku 4.5 | $0.00007 | $0.00209 |
Grade A, and why
avalonia-pro-max/layout-patterns 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 4d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Layout Patterns
Breakpoints
Avalonia desktop windows have no fixed viewport, so define your own breakpoint conventions and react in code-behind or via OnSizeChanged. Recommended scale:
| Name | Width | Typical |
|---|---|---|
Compact |
< 640 px | Mobile, narrow sidebar collapsed window |
Medium |
640 – 1024 px | Tablet, small desktop window |
Wide |
1024 – 1440 px | Standard desktop |
XWide |
≥ 1440 px | Large desktop, ultrawide |
private void OnSizeChanged(object? sender, SizeChangedEventArgs e)
{
var classes = (Window)this;
classes.Classes.Set("compact", e.NewSize.Width < 640);
classes.Classes.Set("medium", e.NewSize.Width >= 640 && e.NewSize.Width < 1024);
classes.Classes.Set("wide", e.NewSize.Width >= 1024 && e.NewSize.Width < 1440);
classes.Classes.Set("xwide", e.NewSize.Width >= 1440);
}
Then style by class:
<Style Selector="Window.compact StackPanel.sidebar"><Setter Property="IsVisible" Value="False"/></Style>
For more granular containers, use ContainerQuery (see avalonia-styling).
Layout Templates
App Shell — Sidebar + Content + Right Panel
<Grid>
<Grid.ColumnDefinitions>
<ColumnDefinition Width="240"/> <!-- Sidebar -->
<ColumnDefinition Width="*"/> <!-- Main -->
<ColumnDefinition Width="320"/> <!-- Right rail -->
</Grid.ColumnDefinitions>
<Border Grid.Column="0" Background="{DynamicResource SurfaceMutedBrush}">
<!-- nav -->
</Border>
<ScrollViewer Grid.Column="1">
<StackPanel Margin="32" Spacing="{StaticResource Space6}">
<!-- main content -->
</StackPanel>
</ScrollViewer>
<Border Grid.Column="2" Background="{DynamicResource SurfaceBrush}">
<!-- detail / inspector -->
</Border>
</Grid>
Hide the right rail on compact/medium:
<Style Selector="Window.compact Grid > Border:nth-child(3)">
<Setter Property="IsVisible" Value="False"/>
</Style>
Master-Detail with SplitView
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.
- 4d ago First seen · 251 lines · 66 tokens per session scan A 860040c950a0
avalonia-pro-max/layout-patterns is a skill published in the GitHub repository linuxdevel/Avalonia-skills (35 stars, last pushed 4mo ago), licensed MIT. It adds 66 tokens to every session and 2,094 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…