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 v9-abstract-blocksgit 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/v9-abstract-blocks)<a href="https://agentmods.dev/skills/rob-balfre/dryui/v9-abstract-blocks"><img src="https://agentmods.dev/badge/skills/rob-balfre/dryui/v9-abstract-blocks/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/v9-abstract-blocks"><img src="https://agentmods.dev/badge/skills/rob-balfre/dryui/v9-abstract-blocks.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.01777 |
| Opus 5.5 | $0.00017 | $0.00711 |
| Sonnet 5.5 | $0.00008 | $0.00355 |
| Haiku 4.5 | $0.00004 | $0.00178 |
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.
This is a copy
91% identical to dryui-build — 26 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DryUI Layout Blocks: Abstract Shell
Build only an abstract colored block layout skeleton. This is a layout extraction stage, not a UI implementation.
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, copied text, copied metrics, copied dates, copied names, or generated business data.
1. Classify The Task
- Full page: build a page shell with
topbar/navigation,primary, and optionalsecondary,utility,rail,summary,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. Blueprint Before Coding
Write the region plan mentally before editing:
- Mobile: one-column top-to-bottom order.
- Tablet: first useful two-pane/grouped composition.
- Desktop: persistent rail/sidebar, right panels, attached panes, dominant work surface.
Decide:
- Which region is
primary. - Whether spacing is
contiguous,guttered, ormixed. - Which regions are secondary or utility, so they do not become larger than
primary. - Which visible bands are shell regions versus nested primitives.
3. Use Recipes Only For Proportions
Do not change required area names for a recipe.
- Dashboard: summary strip, primary chart/workspace, insights/activity.
- Board/Kanban: board is
primary; task detail issecondary; activity isutility; desktop rail if present. - CRM: table/pipeline is
primary; account/detail issecondary; forecast/activity are utility. - Settings/Admin: settings/profile/form stack is
primary; help/status/activity are secondary/utility; compact actions; desktop rail if present. - Knowledge/Document Reader: reader is
primary; collections/list are navigation/secondary; AI summary is secondary/utility; reader must be largest at desktop.
4. Markup Contract
For a full page, use this direct-child shape:
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 · 164 lines · 42 tokens per session scan A ce475cecabff
dryui-build is a skill published in the GitHub repository rob-balfre/dryui (9 stars, last pushed 5mo ago), licensed MIT. It adds 42 tokens to every session and 1,777 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to dryui-build, differing in 26 lines, and is treated as a copy.
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".