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-a-branching-task-listgit 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-a-branching-task-list)<a href="https://agentmods.dev/skills/rob-balfre/dryui/variant-a-branching-task-list"><img src="https://agentmods.dev/badge/skills/rob-balfre/dryui/variant-a-branching-task-list/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-a-branching-task-list"><img src="https://agentmods.dev/badge/skills/rob-balfre/dryui/variant-a-branching-task-list.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.00036 | $0.00704 |
| Opus 5 | $0.00018 | $0.00352 |
| Sonnet 5 | $0.00007 | $0.00141 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
dryui-build-experiment-a 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 10d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DryUI Build Experiment A: Branching Task List
Start Here
Before writing code, identify the target:
- Full page
- Section of a page
- Repeated component or list item
- Form or workflow
- Dashboard or data surface
- Polish pass
If more than one applies, follow the most specific branch first. For a dashboard page, follow Dashboard or data surface, then Full page.
Full Page
- Create one root wrapper with a specific
data-layout="<page-name>". - In
src/layout.css, create the matching selector. - Add
container: <page-name> / inline-sizeto the page wrapper. - Put all page-level
display: gridanddisplay: flexinsrc/layout.css. - Use mobile-first base layout.
- Use
@container <page-name> (...)for responsive shifts. - Do not use
@mediafor layout breakpoints. - Do not put color, background, border, shadow, text, position, z-index, width, height, or inline-size in
src/layout.css. - Use
data-layout-areafor children that participate in named grid areas. - Verify mobile and desktop screenshots.
Dashboard Or Data Surface
- Name the primary user task: monitor, compare, triage, configure, report, or act.
- Choose density: compact, standard, or spacious.
- Define regions before markup:
- header
- filters/actions
- summary metrics
- primary visualization
- data table or detail list
- secondary detail/action area if needed
- Use named grid areas when regions need stable placement.
- Prefer data hierarchy over decorative cards.
- Use cards only for distinct interactive or comparable units.
- Use
TableorDataGridfor tabular data. - Use
ChartorSparklinefor chart content. - Include loading, empty, error, disabled, and dense-data states.
- Test long labels, many rows, narrow containers, and primary action visibility after collapse.
Section Of A Page
- Add a specific
data-layout="<section-name>". - Scope section layout in
src/layout.css. - Use the parent page container unless the section needs independent responsive behavior.
- Do not create a second container query by default.
- Ensure the section works when surrounding content changes.
What ships with it
1 file 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.
- 10d ago First seen · 83 lines · 36 tokens per session scan A b54aed30d545
dryui-build-experiment-a is a skill published in the GitHub repository rob-balfre/dryui (9 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 704 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…