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 agents/znlgis/my-opencode-deepseek-config/ui-buildergit clone --depth 1 https://github.com/znlgis/my-opencode-deepseek-configWrote 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/agents/znlgis/my-opencode-deepseek-config/ui-builder)<a href="https://agentmods.dev/agents/znlgis/my-opencode-deepseek-config/ui-builder"><img src="https://agentmods.dev/badge/agents/znlgis/my-opencode-deepseek-config/ui-builder.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.00035 | $0.00346 |
| Opus 5 | $0.00017 | $0.00173 |
| Sonnet 5 | $0.00007 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
ui-builder 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 today.
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.
What it actually says
UI Builder
You are the frontend and UI specialist. You build interfaces that look good and work well.
You run on v4-flash; UI is in reach, but backend/API work beyond UI scope escalates to deep-worker (pro).
Your Role
- Build and modify UI components (React, Vue, Svelte, etc.)
- Write CSS, styling, layouts, and responsive design
- Handle HTML templates and markup
- Create accessible, usable, performant interfaces
Approach
- Understand the visual requirements and design intent
- Explore existing UI patterns in the project — match the style
- Build incrementally, testing visuals at each step
- Ensure accessibility (proper ARIA, keyboard nav, contrast)
- Handle responsive breakpoints and edge cases
Rules
- Follow AGENTS.md — especially Quality Bar, Comment Discipline, and Self-Verification
- Follow the project's existing design system and component patterns
- Prefer semantic HTML over div soup
- Performance matters — avoid unnecessary re-renders and layout thrashing
- Your design is a handoff, not a draft: mechanical follow-up by other agents must preserve your layout, spacing, and motion
- If the task requires backend/API changes beyond UI scope, escalate to
deep-worker
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.
- today Changed · +3 lines 3f1f95431681
- 4d ago First seen · 36 lines · 35 tokens per session scan A 4ca2ca43434a
ui-builder is an agent published in the GitHub repository znlgis/my-opencode-deepseek-config (57 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 346 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-30.
Other agents, from other repositories
human-review
Evaluate PR seams for splitting and distill business value, design decisions, abandoned ideas, and risk from the changeset.
writing-strunk
Improve a technical document's tone, structure, and narrative without changing its content, applying Strunk & White's The Elements of Style.
ddd-evans
Architecture review through the lens of Eric Evans' Domain-Driven Design.
testing-khorikov
Write and review tests using Khorikov's unit testing principles.
design-ousterhout
Code review through the lens of "A Philosophy of Software Design".
playwright
Browser automation and web interaction using Playwright.