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 variant-d-agentic-gatedgit 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/variant-d-agentic-gated)<a href="https://agentmods.dev/skills/rob-balfre/dryui/variant-d-agentic-gated"><img src="https://agentmods.dev/badge/skills/rob-balfre/dryui/variant-d-agentic-gated/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/variant-d-agentic-gated"><img src="https://agentmods.dev/badge/skills/rob-balfre/dryui/variant-d-agentic-gated.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.00050 | $0.01406 |
| Opus 5.5 | $0.00020 | $0.00562 |
| Sonnet 5.5 | $0.00010 | $0.00281 |
| Haiku 4.5 | $0.00005 | $0.00141 |
Grade A, and why
dryui-build-experiment-d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DryUI Build Experiment D: Agentic Gated Workflow
Target Router
Before implementation, identify the target:
- Full page: route, screen, dashboard, admin page, settings page, docs page.
- Section: hero, header, sidebar, table area, pricing block, footer.
- Repeated component: card, row, list item, toolbar item, table cell.
- Form/workflow: settings form, wizard, editor, onboarding, destructive action.
- Polish pass: spacing, hierarchy, states, responsive behavior, visual refinement.
If the target is a dashboard or data surface, apply Dashboard Branch first, then Full Page Branch when it is a route or screen.
Target Brief Gate
Write this before code:
Target brief: type=<page|section|component|form|polish>, subtype=<dashboard|docs|marketing|settings|other>, user=<role>, primary_task=<task>, density=<compact|standard|spacious>, required_states=<states>.
Agentic Variant Gate
When the harness supports subagents and the user has asked for exploration, run three parallel variants before committing:
- Structure variant: optimize information architecture, regions, and responsive order.
- Density variant: optimize dashboard density, scan speed, and data hierarchy.
- State/resilience variant: optimize loading, empty, error, long labels, dense rows, and mobile collapse.
Each variant must return:
- Mobile, tablet, and desktop layout plan.
data-layout/data-layout-areastructure.src/layout.cssstructure.- Risk list against DryUI lint and visual checks.
Then score each variant from 1-5 on:
- Task fit.
- DryUI contract.
- Mobile-first/container-query quality.
- Visual hierarchy.
- State coverage.
- Implementation risk.
Pick one winner or merge the strongest parts. Do not average weak variants into a muddled design.
If subagents are unavailable, create the three variants locally as short sketches, then score them before implementation.
Full Page Branch
For a full page:
- Create a page shell with a specific
data-layout="<page-name>-shell". - In
src/layout.css, putcontainer: <page-name> / inline-sizeon the shell. - Put the responsive grid on an inner child, usually
data-layout-area="page". - Write
@container <page-name> (...)rules that style descendants inside the shell; do not rely on a container query to style the container element itself. - Start with mobile-first single-column layout.
- Add tablet and desktop shifts with
@container <page-name> (min-width: ...). - Use
data-layout-areafor stable regions and named grid areas. - Keep
src/layout.cssstructural only: display, grid, flex, container, tokenized spacing, alignment, and block-size constraints. - Keep color, background, border, shadow, radius, typography, position, z-index, width, height, and inline-size out of
src/layout.css.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 153 lines · 50 tokens per session scan A dfac0ac87ff0
dryui-build-experiment-d is a skill published in the GitHub repository rob-balfre/dryui (9 stars, last pushed 5mo ago), licensed MIT. It adds 50 tokens to every session and 1,406 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".