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 DevExpress/agent-skills --skill devexpress-wpf-from-screenshotgit clone --depth 1 https://github.com/DevExpress/agent-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/devexpress/agent-skills/devexpress-wpf-from-screenshot)<a href="https://agentmods.dev/skills/devexpress/agent-skills/devexpress-wpf-from-screenshot"><img src="https://agentmods.dev/badge/skills/devexpress/agent-skills/devexpress-wpf-from-screenshot/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/devexpress/agent-skills/devexpress-wpf-from-screenshot"><img src="https://agentmods.dev/badge/skills/devexpress/agent-skills/devexpress-wpf-from-screenshot.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.00161 | $0.05795 |
| Opus 5.5 | $0.00064 | $0.02318 |
| Sonnet 5.5 | $0.00032 | $0.01159 |
| Haiku 4.5 | $0.00016 | $0.00579 |
Grade A, and why
devexpress-wpf-from-screenshot 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 — 366 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build a DevExpress WPF Screen from a Mockup
Read this file to the end before you act on any of it. If your file-reading tool returned only part of it, call it again for the remaining lines: the consent gates below are what a partial read skips.
One decision repeats: what is a region for, and which control does that? The picture cannot answer it — a static strip and a user-rearrangeable panel look identical. So inspect before choosing, announce before building, check the running window before claiming.
Done means a screen you have seen running. A green build proves nothing — markup compiles and then renders an empty panel, a collapsed region, a window that never appears.
Keep this conversation small, and take fewer, larger steps. Everything you pull into it is carried
through every later step of the run, so what is cheap to read once is not cheap to hold; batch what can
be batched rather than paying for another round trip. Send bulk work to sub-agents and take back
only their conclusion. Images must not accumulate here:
⛔ never open a capture yourself — the render step writes the UI tree as text, so read that; the
images go to the comparison sub-agent and its verdict comes back as words. Locate with
glob/grep, then read only the block you need. Never re-read a file you just wrote. Read a
reference file at the step that needs it, not up front.
Result levels
| Level | Goal | When it applies |
|---|---|---|
| Structure | Every element is there, each built from a control that fits its function, in the right hierarchy, with the real texts; the app runs. There means visible and readable at the size the app opens — an element that exists in the tree but sits off the screen, or in a card whose rows are cut, is not there for the user. Colour is not judged here — but a fill, bar, icon or highlight a control produces from a rule is a feature, not a colour, and so is the text a feature emits by default, so both belong here. | Always |
| Look | It reads as the same screen — layout, proportion, spacing, typography — expressed through the theme the app already uses and through the properties the controls themselves expose. | By default |
| Detail | Exact colours, metrics, fonts and glyphs, and the gaps that can only be closed by overriding theme resources. | On request |
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/api-lookup.md 5.3 KB
- references/compare.md 6.8 KB
- references/control-selection.md 12 KB
- references/figma.md 3.0 KB
- references/inspect-project.md 6.9 KB
- references/mockup-analysis.md 4.0 KB
- references/render-check.md 12 KB
- references/screen-location.md 9.2 KB
- scripts/build-run-capture.ps1 25 KB runs code
- scripts/measure-render.ps1 8.7 KB runs code
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 · 366 lines · 161 tokens per session scan A aeedc07861ac
devexpress-wpf-from-screenshot is a skill published in the GitHub repository DevExpress/agent-skills (66 stars, last pushed 4d ago), licensed MIT. It adds 161 tokens to every session and 5,795 once invoked, about $0.0006 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-20.
Other skills, from other repositories
antislop-ui
UI and visual skill for antislop. Use when building or editing any interface: color, layout, components, motion. Load with the core.
uicraft
Create, improve, audit, and polish distinctive production-grade web interfaces, including marketing/landing pages and personal portfolio sites. Use for UI or frontend design, responsive layouts, typography, color, motion, UX copy, accessibility, performance, design-system alignment, onboarding, edge cases, or visual…
ardot-design-to-code
Use this skill for Ardot canvas tasks that convert a design into frontend code, or extract a design system / style guide from a website. Covers: design-to-code, design → HTML/CSS/JS, export as webpage, pixel-perfect reproduction, generate an Application from a design, slide transitions, responsive scaling; and website…
ardot-ui-design
A workflow for designing user interfaces in the Ardot canvas, including websites, web apps, dashboards, mobile screens, forms, tables, and design systems. A user interface is the screens and controls people use to operate software.
accessibility-standards
WCAG 2.2 AA rules for HTML, CSS and React: contrast, keyboard, screen-reader semantics, voice access, forms and tables. Use when building or changing UI components, forms, navigation or any user-facing element.
frontend-design
Visual direction for distinctive pages: a named aesthetic, type pairing, color and spacing tokens, and motion. Use when designing a landing page, marketing site or UI theme where the look itself matters, not when scaffolding components.