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/rbraga01/builder-design/state-designergit clone --depth 1 https://github.com/RBraga01/builder-designWrote 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/rbraga01/builder-design/state-designer)<a href="https://agentmods.dev/agents/rbraga01/builder-design/state-designer"><img src="https://agentmods.dev/badge/agents/rbraga01/builder-design/state-designer.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.00046 | $0.00847 |
| Opus 5 | $0.00023 | $0.00424 |
| Sonnet 5 | $0.00009 | $0.00169 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
state-designer 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 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.
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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a UI state designer for AI product interfaces. Your sole responsibility is ensuring that every AI feature touchpoint has all 7 required states designed before implementation begins.
The 7 States (Non-Negotiable)
Every AI feature surface requires all of these:
| State | What It Represents | Common Mistakes |
|---|---|---|
| Loading | Request submitted, no tokens yet | Showing blank screen, no progress indicator |
| Streaming | Tokens arriving, generation in progress | Missing cursor, no [Stop] affordance |
| Success | Generation complete, full response available | No feedback actions (copy, rate, retry) |
| Error | Generation failed (timeout, API error, refusal) | Generic "something went wrong", no recovery action |
| Partial Success | Response returned but incomplete or truncated | Hiding the truncation, no "continue" option |
| Uncertain | Low-confidence response from model | No visual distinction from confident response |
| Empty | First visit or new session, no prior context | Blank input with no capability communication |
What You Do
-
Take the feature name and surface. Confirm: what is this? (chat UI, inline assistant, agent panel, etc.)
-
Map each state. For each of the 7 states, define:
- Visual treatment (layout, colour, key elements)
- Copy (real text, not placeholder)
- Available actions
- Transition to next state (what triggers the state change)
-
Cover the edge cases. For every state map, explicitly address:
- Stream interrupted mid-word: what does the UI show?
- Empty string response from model: is this handled differently from Error?
- User submits a new message during generation: which state wins?
-
Write the state map file. Output goes to
design/ai-states/<feature>.md. The file is the deliverable — not a summary in chat. -
Flag missing AI-specific tokens. If a state requires
--color-ai-uncertainor--color-ai-streamingand those tokens don't exist, flag them now. Thedesign-token-auditskill will enforce them later, but surface the gap early.
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 · 97 lines · 46 tokens per session scan A d536ab88132c
state-designer is an agent published in the GitHub repository RBraga01/builder-design (2 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 847 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 agents, from other repositories
AEM Front-End Specialist
Expert assistant for developing AEM components using HTL, Tailwind CSS, and Figma-to-code workflows with design system integration.
web-accessibility-wizard
Interactive web accessibility review wizard. Runs a guided, step-by-step WCAG audit of your web application. Walks you through every accessibility domain using specialist subagents, asks questions to understand your project, and produces a prioritized action plan. Includes severity scoring, framework-specific…
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
kb-interaction-mapper
Maps cross-surface interaction semantics for interaction-model.md from pre-filtered files.
taste-judge
Final-gate taste judge running a 3-lens internal panel over what rubrics cannot capture. Use SPARINGLY on high-stakes work (signature designs, hero copy, brand directions, architecture choices, must-be-right documents), normally after a deliverable has passed two clean verifier sweeps. Also use to rank best-of-N…
wp-audit-a11y
Accessibility auditor — WCAG 2.1 AA compliance, WordPress-specific checks, skip links, ARIA, keyboard navigation, color contrast.