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 v11b-recipes-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/v11b-recipes-first)<a href="https://agentmods.dev/skills/rob-balfre/dryui/v11b-recipes-first"><img src="https://agentmods.dev/badge/skills/rob-balfre/dryui/v11b-recipes-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/v11b-recipes-first"><img src="https://agentmods.dev/badge/skills/rob-balfre/dryui/v11b-recipes-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.00035 | $0.01070 |
| Opus 5 | $0.00017 | $0.00535 |
| Sonnet 5 | $0.00007 | $0.00214 |
| Haiku 4.5 | $0.00003 | $0.00107 |
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 11d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DryUI Full Page: Recipes First
Implement the supplied design image as a real, responsive DryUI app page. Pick the closest recipe first, then code.
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.
Only edit src/routes/+page.svelte, src/layout.css, and src/app.css if global body/font cleanup is needed.
Pick One Recipe
Dashboard:
- Desktop: rail or top nav, metric/summary band, dominant chart/workspace, right activity/insight.
- Tablet: topbar plus two-column content, summary above primary.
- Mobile: topbar, navigation, summary, primary, secondary/utility.
Board/Kanban:
- Desktop: navigation rail, board as primary with horizontal columns, inspector/activity as secondary.
- Tablet: compact rail plus board and inspector stacked or side-by-side.
- Mobile: topbar, nav/status filters, primary board list, secondary details.
CRM/Pipeline:
- Desktop: rail/nav, summary strip, table/pipeline as primary, detail or forecast as secondary.
- Tablet: summary plus table, secondary stacked.
- Mobile: filters, summary cards, primary list/table rows, secondary below.
Settings/Admin:
- Desktop: left rail or settings nav, primary forms/content, secondary status/help, actions fixed to shell edge if present.
- Tablet: navigation band, primary content, secondary cards.
- Mobile: topbar, navigation grid, primary sections, secondary, utility, actions.
Knowledge/Document:
- Desktop: navigation/list, reader/workspace primary, assistant/details utility.
- Tablet: navigation beside reader, utility below or narrow side.
- Mobile: topbar, navigation, secondary/list, primary reader, utility/actions.
Build Rules
- Use DryUI
Button,Input,Badge,Table,Tabs,Separator, and simple static Svelte markup. - Avoid component APIs you have not checked.
- Use believable content and short labels, not exact copied mockup data.
- Keep repeated controls dense and scannable.
- Use icons from
lucide-svelteonly where they clarify buttons or navigation. - Use light, readable app-owned colors unless the reference is explicitly dark.
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.
- 11d ago First seen · 117 lines · 35 tokens per session scan A 451269cc9852
dryui-build is a skill published in the GitHub repository rob-balfre/dryui (9 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 1,070 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…
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json…
popular-web-designs
54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.
anti-ui-slop
Stop coding agents from shipping generic UI. Extend the product's design system, use UIZZE evidence only when useful, cover required states, and inspect the rendered result.
shadcn-ui-flutter
A comprehensive Flutter UI library inspired by shadcn/ui. Provides high-quality, customizable, and accessible components including Buttons, Cards, Forms, and more. Use this skill when building Flutter UIs, implementing design systems, or needing specific component usage examples.