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 rob-balfre/dryui --skill v6-hybrid-layoutgit clone --depth 1 https://github.com/rob-balfre/dryuiWrote 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/rob-balfre/dryui/v6-hybrid-layout)<a href="https://agentmods.dev/skills/rob-balfre/dryui/v6-hybrid-layout"><img src="https://agentmods.dev/badge/skills/rob-balfre/dryui/v6-hybrid-layout/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/rob-balfre/dryui/v6-hybrid-layout"><img src="https://agentmods.dev/badge/skills/rob-balfre/dryui/v6-hybrid-layout.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.00042 | $0.01250 |
| Opus 5 | $0.00021 | $0.00625 |
| Sonnet 5 | $0.00008 | $0.00250 |
| Haiku 4.5 | $0.00004 | $0.00125 |
Grade A, and why
dryui-build 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 12d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DryUI Layout Blocks: Hybrid Contract
Build only a colored block layout skeleton. Do not recreate detailed UI.
Only edit:
src/routes/+page.sveltesrc/layout.css
Do not import anything. Do not use DryUI components, Lucide, icons, SVGs, images, charts, tables, forms, buttons, inputs, avatars, realistic widgets, or generated data.
1. Classify The Task
- Full page: build a page shell with
topbar/navigation,primary, and optionalsecondary,utility,rail,actions. - Page section: build a section shell with
primaryand optional adjacent regions.
For full-page design-image references, treat the whole image as the page shell.
2. Make A Breakpoint Blueprint Before Coding
Infer the same region set at all breakpoints:
- Mobile: one-column order from top to bottom.
- Tablet: first grouping when there is room for side-by-side panes.
- Desktop: persistent rails, side panels, and dominant work surface from the reference.
For each breakpoint, decide:
- Which regions are visible.
- Which regions become rails or side panels.
- Which region is
primary. - Whether the spacing is
contiguous,guttered, ormixed.
3. Pick The Closest Recipe
Use recipes for proportion decisions only. Do not replace required area names.
- Dashboard: topbar/nav, KPI or summary strip, primary chart/workspace, insights/activity/utilities.
- Board/Kanban: topbar, tabs/toolbar, dominant board as
primary, task/detail assecondary, activity asutility, desktop rail if present. - CRM/Record Workspace: nav, workspace header, KPI strip, table/pipeline as
primary, account/detail assecondary, forecast/activity asutility. - Settings/Admin: nav/topbar, settings/profile/form stack as
primary, help/status/activity assecondaryorutility, compactactions, desktop rail if present. - Knowledge/Document Reader: collections/list as navigation/secondary, document reader as
primary, AI summary assecondary; the reader must be the largest desktop region.
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.
- 12d ago First seen · 128 lines · 42 tokens per session scan A 72f6ab8510d6
dryui-build is a skill published in the GitHub repository rob-balfre/dryui (9 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 1,250 once invoked, about $0.0002 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-31.
Other skills, from other repositories
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality and accessible markup. Use this skill when the user asks to build or beautify web components, pages, applications, landing pages, dashboards, artifacts, or React/HTML/CSS UI. Generates creative, polished code that avoids generic AI…
shadcn-sveltekit-design
Use when building, redesigning, beautifying, or refactoring SvelteKit pages and reusable components with shadcn-svelte, Bits UI, or the shadcn-svelte MCP. Trigger on landing pages, dashboards, marketing sites, app shells, forms, navbars, tables, dialogs, responsive layouts, theming, icon selection, and requests to…
popular-web-designs
54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.
oat-css
Our preferred CSS framework — ultra-lightweight, semantic HTML UI library (8KB). Style web UIs with semantic HTML and minimal classes. Override with app-level SCSS only when necessary.
component-search
Search 21st.dev component registry for production-ready React components. Finds components by natural language description, filters by framework and style system, returns ranked results with install instructions. Use when looking for UI components, finding alternatives to existing components, or sourcing design system…
polish-ui
Design-quality workflow that combines design taste, aesthetic direction, image-to-code, a Web Interface Guidelines audit, and real-browser verification. Use when building or polishing a UI surface, implementing a mockup/screenshot, or when asked to make a page "look great".