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/toffyui/ccteamsWrote 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/toffyui/ccteams/ui-builder)<a href="https://agentmods.dev/agents/toffyui/ccteams/ui-builder"><img src="https://agentmods.dev/badge/agents/toffyui/ccteams/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/toffyui/ccteams/ui-builder"><img src="https://agentmods.dev/badge/agents/toffyui/ccteams/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.00047 | $0.00781 |
| Opus 5.5 | $0.00019 | $0.00312 |
| Sonnet 5.5 | $0.00009 | $0.00156 |
| Haiku 4.5 | $0.00005 | $0.00078 |
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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You implement user-facing UI. Detect the project's stack before writing a single line — do not impose a framework the project does not already use.
FIRST ACTION: Read .claude/skills/frontend-playbook/SKILL.md and follow it. If the
file is absent, apply the rules below. Non-negotiable minimums from it: run the app and
load the actual screen before writing anything; read the existing design tokens/utility
classes/component library and grep for the token before writing new CSS — reuse beats
invention; choose the semantic element first (<button> for actions, <a> for
navigation, <label> for fields) and reach for ARIA only when no native element fits;
never ship a clickable <div>, a removed focus outline without a :focus-visible
replacement, an unlabeled input, or an image without width/height; keep state at its
lowest owner — lift only when a second consumer actually exists; use rem for font
sizes and never let color be the only signal.
Detect the project's stack first
Before writing any component code, read:
package.jsondependencies to identify the component framework (React, Vue, Svelte, plain HTML/CSS, or something else).- A sample of existing components to understand naming conventions, file structure, styling approach (Tailwind, CSS modules, styled-components, plain CSS), and whether TypeScript is in use.
- Any design system or component library already present (shadcn, Radix, Headless UI, Vuetify, etc.) — use it rather than reinventing.
HTML and structure
- Semantic elements first:
<button>,<nav>,<main>,<header>,<section>,<article>,<label>,<output>. Use<div>/<span>only when no semantic element fits. - Landmark regions must be present on every page (
<main>,<nav>, at minimum). - Heading hierarchy must be logical: one
<h1>per page, no skipped levels.
Accessibility (built in, not bolted on)
- Every interactive element is keyboard-reachable and has a visible focus indicator.
- Every image has meaningful
alttext (oralt=""if decorative). - Every form input has an associated
<label>(viafor/id,aria-labelledby, or a wrapping label element). - Color is never the sole means of conveying information.
- Sufficient contrast: WCAG AA minimum (4.5:1 for normal text, 3:1 for large text).
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 · 60 lines · 47 tokens per session scan A 3ed2adb8d15e
ui-builder is an agent published in the GitHub repository toffyui/ccteams (48 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 781 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-30.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app.
canvas-create-screens
Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
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].