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 v25a-crm-density-guardgit 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/v25a-crm-density-guard)<a href="https://agentmods.dev/skills/rob-balfre/dryui/v25a-crm-density-guard"><img src="https://agentmods.dev/badge/skills/rob-balfre/dryui/v25a-crm-density-guard/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/v25a-crm-density-guard"><img src="https://agentmods.dev/badge/skills/rob-balfre/dryui/v25a-crm-density-guard.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.00051 | $0.03367 |
| Opus 5 | $0.00026 | $0.01684 |
| Sonnet 5 | $0.00010 | $0.00673 |
| Haiku 4.5 | $0.00005 | $0.00337 |
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.
This is a copy
78% identical to dryui-build — 70 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DryUI Page Layout: CRM-Density With Preview Guard
Build the supplied design image as a concise DryUI app page. Optimize for clean build output, lint-safe layout, responsive shell fidelity, and a readable first viewport before visual embellishment.
Harness Rule
Run bun run build before final. Do not run dev servers, browser checks, extra audits, or broad package searches. The harness captures mobile, tablet, and desktop after you finish.
Work fast:
- Read the design image once, pick the closest recipe, then edit the three files directly.
- Do not inspect package internals unless
bun run buildreports a missing import. - Prefer compact arrays plus
{#each}loops over repeated markup. - If uncertain about a visual detail, preserve the page structure and use clear text evidence rather than inventing a complex widget.
Stage 1: Pick One Recipe And Budget
Identify the page as one of these recipes and keep the fixed shell:
dashboard: one metric grid, one evidence panel, one activity panel, and up to two secondary insight panels.settings: one nav, two primary form/status panels, and up to two secondary help/billing/activity panels.crm: one metric grid, one deals panel, choose exactly one forecast/account panel, and one compact secondary activity/customer panel.kanban: one nav, one board grid with three columns and one card per column, plus up to two secondary detail/activity panels.knowledge: one light collections panel, one documents/results panel, one selected-document panel, and up to two secondary AI/source panels.
Hard budget: after the topbar and navigation, use no more than five top-level panels/cards total. A grid of metrics counts as one panel. Do not add storage, extra status, duplicate activity, or extra summary panels unless they replace another panel.
Mobile density budget:
- Target a useful mobile first viewport and keep the full mobile document under roughly 2800px tall.
- Use short mobile-safe page names in the topbar. If a title would wrap awkwardly in 320px, shorten it, for example
KnowledgebecomesKnowledge Baseonly when it fits, otherwiseKnowledge. - Do not let a single hero image, preview, or document mock consume the mobile page. Keep media as supporting evidence, not the main height driver.
- Prefer two compact secondary panels over three long panels. If the reference has many side utilities, merge them into one compact summary panel and one compact sources/activity panel.
- For settings pages, use two primary panels and at most two secondary panels. Each secondary panel should have at most two rows.
- For CRM pages, use four top-level panels after the topbar/nav: metric grid, deals, forecast or account, and one compact secondary. Do not include both a forecast panel and a full account/customer panel. If the reference shows both, merge the account/customer facts into the secondary panel.
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 · 291 lines · 51 tokens per session scan A eae075474c76
dryui-build is a skill published in the GitHub repository rob-balfre/dryui (9 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 3,367 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 78% identical to dryui-build, differing in 70 lines, and is treated as a copy.
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".