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 v11a-contract-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/v11a-contract-first)<a href="https://agentmods.dev/skills/rob-balfre/dryui/v11a-contract-first"><img src="https://agentmods.dev/badge/skills/rob-balfre/dryui/v11a-contract-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/v11a-contract-first"><img src="https://agentmods.dev/badge/skills/rob-balfre/dryui/v11a-contract-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.00043 | $0.01163 |
| Opus 5 | $0.00022 | $0.00581 |
| Sonnet 5 | $0.00009 | $0.00233 |
| Haiku 4.5 | $0.00004 | $0.00116 |
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 9d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DryUI Full Page: Contract First
Build a real DryUI page from the supplied design image. This is not a colored-block skeleton, but the page must start from the same strict layout contract.
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.sveltesrc/layout.csssrc/app.cssonly for global font/body polish if needed
Stage 1: Extract The Layout
Before coding, classify the target:
dashboard: summary, chart/workspace, side insight/activity.board: rail/nav, board columns as primary, inspector/activity as secondary.crm: pipeline/table as primary, detail/forecast/activity as secondary or utility.settings: form/content stack as primary, help/status/actions as secondary/utility.knowledge: reader/workspace as primary, list/navigation and assistant/details around it.
Decide:
- Mobile order.
- Tablet grouping.
- Desktop shell.
- Whether adjacent sections touch (
gap: 0) or have visible gutters. - Which region is the largest desktop
primary.
Stage 2: Build Real UI
Use DryUI components for controls and UI primitives:
- Prefer
Button,Input,Badge,Table,Tabs, andSeparator. - Use raw semantic elements for shell regions, headings, text, cards, charts, and decorative rectangles.
- Do not use raw
<button>,<input>,<select>,<textarea>,<form>, or<table>when a DryUI component exists. - Use realistic but concise content. Do not copy long mockup text, exact numbers, dates, names, or private-looking data from the image.
- Keep the UI compact and work-focused. Avoid marketing hero sections, oversized cards, and decorative background blobs.
- Use app-owned light surfaces for the page unless the reference is explicitly dark.
Markup Contract
Use one page shell:
<main data-layout="<page-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.
- 9d ago First seen · 124 lines · 43 tokens per session scan A 0fe311e5e5ac
dryui-build is a skill published in the GitHub repository rob-balfre/dryui (9 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 1,163 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
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.
design
Use when the user wants the visual/experiential design of a product done systematically — a design system, a screen, a landing page, or a visual identity — grounded in researched real-world prior art and free of AI slop. Establishes/extends the design system, invokes the matching local taste skill, dispatches the…