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 agentmods add skills/rob-balfre/dryui/basenpx skills add rob-balfre/dryui --skill basegit 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/base)<a href="https://agentmods.dev/skills/rob-balfre/dryui/base"><img src="https://agentmods.dev/badge/skills/rob-balfre/dryui/base.svg" alt="Measured on agentmods" 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 | $0.00062 | $0.01897 |
| Opus 5 | $0.00031 | $0.00949 |
| Sonnet 5 | $0.00012 | $0.00379 |
| Haiku 4.5 | $0.00006 | $0.00190 |
Grade C, and why
dryui-build scanned grade C with 1 finding 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 4d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
- `<!-- svelte-ignore ... -->` Copies of this mod
8 near-identical copies found in the catalogue:
- dryui-build — 100% identical, 0 lines differ
- dryui-build — 88% identical, 32 lines differ
- dryui-build — 84% identical, 54 lines differ
- dryui-build — 84% identical, 32 lines differ
- dryui-build — 84% identical, 35 lines differ
- dryui-build — 81% identical, 68 lines differ
- dryui-build — 81% identical, 80 lines differ
- dryui-build — 80% identical, 79 lines differ
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DryUI Build
Build real Svelte 5 UI with DryUI. This skill is only for UI implementation and polish. It does not install DryUI, scaffold projects, run live feedback, or resolve feedback submissions.
Lint First
DryUI lint rules are the contract. If lint, the compiler, or component metadata disagrees with a visual idea, restructure the markup or CSS instead of bypassing the rule.
- Use
@dryui/uiprimitives when DryUI provides one. Do not recreate controls with raw HTML. - DryUI does not ship a layout component. Use plain markup with
data-layoutanddata-layout-area. - Page and section layout lives in
src/layout.css, scoped under[data-layout='<name>']. - All consumer
display: gridanddisplay: flexdeclarations live insrc/layout.cssor@containerblocks inside it. - In
src/layout.css, use only lint-safedisplayvalues such asgridorflex; never adddisplay: block,contents,flow-root, or reset-style display values. - Route and component
<style>blocks must not contain page-leveldisplay: grid,display: flex, layout breakpoints, inlinestyle=, or Sveltestyle:directives. - Responsive layout is mobile-first and uses
@container page (...); never@mediafor layout breakpoints. src/layout.cssis structural only: display, grid, flex, container, tokenized spacing, alignment, and block-size constraints. No color, background, border, shadow, opacity, transition, transform, font, text, position, z-index, width, height, or inline-size.- Visual CSS belongs in app/component CSS and uses real
--dry-*tokens such as--dry-color-bg-base,--dry-color-text, and--dry-color-border, or app-owned custom properties. - In app/component CSS, constrain replaced media and text inside media-backed grids so intrinsic image size or long headings cannot enlarge grid tracks: use
inline-size: 100%,max-inline-size: 100%,min-inline-size: 0,object-fit, and readablemax-width/maxMeasurewhere needed. - Set
body { font-family: var(--dry-font-sans); }insrc/app.cssso dialogs, popovers, and top-layer UI inherit the app font.
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.
- 4d ago First seen · 101 lines · 62 tokens per session scan C 749f93f9f5e7
dryui-build is a skill published in the GitHub repository rob-balfre/dryui (9 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 1,897 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). 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-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…
svelte-docs
Svelte 5.x + SvelteKit 2.x — runes, components, stores, transitions, SSR, routing, TypeScript.
sveltekit-best-practices
SvelteKit and Svelte 5 done right. Runes, load functions, form actions, SSR patterns, and modern Svelte.
svelte-core-bestpractices
Svelte best practices for writing, editing, or reviewing Svelte/SvelteKit components and modules. Use when touching Svelte reactivity, props, events, snippets, each blocks, styling, context, actions/attachments, stores, or Svelte 5 runes.
svelte-core-bestpractices
Guidance on writing fast, robust, modern Svelte code. Load this skill whenever in a Svelte project and asked to write/edit or analyze a Svelte component or module. Covers reactivity, event handling, styling, integration with libraries and more.