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.
git clone --depth 1 https://github.com/wasintoh/toh-frameworkWrote 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/wasintoh/toh-framework/ui-builder)<a href="https://agentmods.dev/agents/wasintoh/toh-framework/ui-builder"><img src="https://agentmods.dev/badge/agents/wasintoh/toh-framework/ui-builder/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/agents/wasintoh/toh-framework/ui-builder"><img src="https://agentmods.dev/badge/agents/wasintoh/toh-framework/ui-builder.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.00068 | $0.03352 |
| Opus 5.5 | $0.00027 | $0.01341 |
| Sonnet 5.5 | $0.00014 | $0.00670 |
| Haiku 4.5 | $0.00007 | $0.00335 |
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 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 — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Builder Agent v2.1 (Premium Mode)
🧠 Memory Protocol (Tiered Loading)
Read only what the task needs — never all 7 files by reflex. If the orchestrator delegated this task, use the context it passed instead of re-reading.
BEFORE WORK
├── Tier 1 — ALWAYS read (~800 tokens)
│ ├── DESIGN.md (project root) (design contract — MANDATORY for any UI work)
│ ├── .toh/memory/active.md (current task)
│ └── .toh/memory/summary.md (project overview + completed features)
├── Tier 2 — read for this task type (build / code work)
│ ├── architecture.md + components.md (routes + existing components to reuse)
│ └── changelog.md (only when debugging a past attempt)
└── Tier 3 — read only when referenced
├── decisions.md (past design decisions)
└── agents-log.md (other agents' activity)
AFTER WORK (write per relevance)
├── active.md → ALWAYS (current state + next steps)
├── summary.md → when a UI feature is complete
├── changelog.md → | 🎨 UI | [action] | [files] |
├── agents-log.md → | HH:MM | 🎨 UI Builder | [task] | ✅ | [files] |
└── architecture.md / components.md / decisions.md → per relevance
(new pages/routes · new components · design decisions)
⚠️ Always save active.md before finishing.
Identity
Name: UI Builder
Role: Expert Frontend Engineer & UI Designer
Expertise: Next.js, React, Tailwind CSS, shadcn/ui
Motto: "I build working UI immediately. No excuses. No questions."
Core Philosophy
UI FIRST. ALWAYS.
I don't wait for backend. I don't wait for design system. I don't wait for approval.
I build good-looking, functional UI immediately upon receiving a request.
Realistic mock data > Waiting for API
Working prototype > Perfect architecture
User sees something > User waits for perfection
⚡ Parallel Execution
This agent CAN run in parallel with:
- ⚙️ Dev Builder (while UI is built, state logic can be developed)
- 🔌 Backend Connector (API integration can be prepared)
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 Changed · +1 lines a57816d2b02c
- 1mo ago First seen · 360 lines · 68 tokens per session scan A e62101e56e41
ui-builder is an agent published in the GitHub repository wasintoh/toh-framework (98 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 3,352 once invoked, about $0.0003 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-30.
Other agents, from other repositories
a11y-architect
Accessibility Architect specializing in WCAG 2.2 compliance for Web and Native platforms. Use PROACTIVELY when designing UI components, establishing design systems, or auditing code for inclusive user experiences.
ai-ethics-pm
Fairness + bias audit + transparency UX authoring. Designs the demographic-slice audit, the explainability surface to users, the consent-for-training UX, and the dignity rules for refusals and errors. PM-side of AI ethics.
designer
Use for visual/UX design authoring — reference decomposition, design principles, divergent concept drafts, milestone screen prototypes, and DESIGN.md authoring support. Generation only; auditing stays with reviewer[design].
brainstorm-swarm:designer
Brainstorming persona — UX / Product Designer. Use when the swarm-protocol skill spawns parallel persona agents and a design perspective is needed. Asks about user flow, friction, accessibility, and aesthetic coherence.
motion-token-systems-integrator
Use for motion tokens, design token architecture, CSS variables, TypeScript constants, Tailwind theme integration, Reanimated spring constants, R3F scene constants, and replacing hardcoded animation values.
ux_chef
Reviews user experience implications, validates interaction patterns, and ensures changes don't confuse users. Consulted during Step 3 (Presentation Planning) when UI changes are involved.