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 v11c-density-firstgit 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/v11c-density-first)<a href="https://agentmods.dev/skills/rob-balfre/dryui/v11c-density-first"><img src="https://agentmods.dev/badge/skills/rob-balfre/dryui/v11c-density-first/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/v11c-density-first"><img src="https://agentmods.dev/badge/skills/rob-balfre/dryui/v11c-density-first.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.00044 | $0.00967 |
| Opus 5.5 | $0.00018 | $0.00387 |
| Sonnet 5.5 | $0.00009 | $0.00193 |
| Haiku 4.5 | $0.00004 | $0.00097 |
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 1mo 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DryUI Full Page: Density First
Build a finished DryUI app page from the design image. Treat the reference as an operational product screen, not a landing page.
Experiment Harness Rule
Run bun run build before finishing. Do not run bun run dev, bun run check, or a long-running screenshot/browser server during the agent step; the experiment harness performs browser capture and visual scoring after you finish.
Edit only src/routes/+page.svelte, src/layout.css, and src/app.css if needed.
Non-Negotiables
- The page must feel like a usable app screen on the first viewport.
- No landing hero, marketing copy, decorative gradients, or oversized editorial cards.
- Desktop must use the canvas. A 1440px viewport should not show a tiny app mockup with blank space around it.
- Mobile must be intentionally summarized. Do not stack every desktop cell or row if it creates a wasteful scroll dump.
- Match whether the reference has gutters. If panes touch, set shell or nested
gap: 0; if separated, use DryUI space tokens.
Three Passes
- Structure: identify shell areas, primary task, mobile order, tablet grouping, and desktop panes.
- Components: implement a real page using DryUI components and compact static content.
- Repair: build, check 390/820/1440, then fix density, contrast, overflow, and whitespace.
DryUI Component Set
Use this safe component set:
Buttonfor commands and icon buttons.Inputfor search/filter fields.Badgefor statuses and compact metadata.Tablefor tabular CRM or activity rows.Tabsfor modes or grouped sections.Separatorfor dense panel separation.
Avoid uncertain APIs. Use static layout blocks for charts, boards, timelines, and document previews.
Shell Contract
Use one shell:
<main data-layout="<type>-shell">
<div data-layout-area="page">
<header data-layout-area="topbar">...</header>
<nav data-layout-area="navigation">...</nav>
<section data-layout-area="primary">...</section>
<aside data-layout-area="secondary">...</aside>
</div>
</main>
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.
- 1mo ago First seen · 100 lines · 44 tokens per session scan A 073a8414364f
dryui-build is a skill published in the GitHub repository rob-balfre/dryui (9 stars, last pushed 5mo ago), licensed MIT. It adds 44 tokens to every session and 967 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
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, charts, sidebars, auth screens, blocks, responsive layouts…
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…
popular-web-designs
54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.
tamagui-v6-config
Tamagui v6 theme system: the light/dark/accent/brand/inverse/level/active theme family, the background-active one-off key, and recipe-tree authoring with createV6Config. Use when choosing a theme for a surface, building a selected/emphasis state, or authoring a custom v6 colors pack.
tamagui-theme-generator
Generate custom Tamagui themes, color palettes, and preview URLs. Use when creating or refining a color scheme, authoring light/dark palettes with brand accents, or previewing generated themes in the browser.
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".