agentmods.dev

ux-mockup

ux-mockup is a command for coding agents from rajconnects/founder-stack. It costs 63 tokens per session (847 once invoked), scanned A, original, MIT.

A command that turns a wireframe into a detailed screen design in Figma. Figma is a collaborative tool for creating and reviewing interface designs.

In plain words
What is it for?
Use it for an explicitly named UX scope after its wireframe is complete, then ask a person to approve, revise, or reject the mockup before marking it ready for implementation.
Why use it?
It lets people inspect and approve the intended visual result before frontend development begins.

Command

Part of the founder-stack plugin — 21 commands, 13 agents shipped together

not rated 2 1mo ago A scan 63 tokens original MIT
View the source file rajconnects/founder-stack
Install

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.

agentmods
npx agentmods add commands/rajconnects/founder-stack/ux-mockup
Clone the repo
git clone --depth 1 https://github.com/rajconnects/founder-stack

Or install founder-stack, the plugin that ships this one along with the rest of its 21 commands, 13 agents.

Wrote 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.

agentmods badge for ux-mockup

README.md
[![agentmods](https://agentmods.dev/badge/commands/rajconnects/founder-stack/ux-mockup.svg)](https://agentmods.dev/commands/rajconnects/founder-stack/ux-mockup)
Your own site
<a href="https://agentmods.dev/commands/rajconnects/founder-stack/ux-mockup"><img src="https://agentmods.dev/badge/commands/rajconnects/founder-stack/ux-mockup.svg" alt="Measured on agentmods" height="20"></a>
Per session 63 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 847 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00063 $0.00847
Opus 5 $0.00032 $0.00424
Sonnet 5 $0.00013 $0.00169
Haiku 4.5 $0.00006 $0.00085

Measured 3d ago against content hash 720aa9fc605d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ux-mockup 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 3d 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.

workflow/commands/ux-mockup.md · 42 lines

How it starts

The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are running the mockup step of the UX design layer. This step ends with a human approve/iterate/reject prompt — you do not approve on the operator's behalf.

Arguments: $ARGUMENTS

Steps

  1. Resolve scope. Parse $ARGUMENTS. The scope label is required — there is no auto for mockup work, since high-fidelity needs an explicit target. If empty: fail loudly: ux-mockup requires an explicit scope. Example: /ux-mockup OnboardingForm.

  2. Compute the scope slug. Same slugification as /ux-wireframe.

  3. Verify wireframe prerequisite. Check for .claude/.ux-wireframe-passed-<scope-slug>. If missing: fail: No wireframe marker for <scope>. Run /ux-wireframe <scope> first. Do not proceed.

  4. Resolve config and inline. Read .claude/project.json once. Extract: design_system.components_spec, design_system.flow_spec, design_system.tokens, design_system.figma.file_key, design_system.figma.screens, stack.frontend. If stack.frontend is null, fail. If figma.file_key is null AND --skip-when-trivial is NOT set, fail: ux-mockup requires figma.file_key to produce mockup frames. Pass --skip-when-trivial to skip Figma writes and proceed straight to approval.

  5. Launch ux-mockup-designer with a self-contained prompt containing: the scope label and slug, the inlined config fields above, the --source reference (if any), and the --skip-when-trivial flag (if any). Do NOT ask the agent to re-read project.json.

  6. Print the agent output verbatim.

  7. Run the approve/iterate/reject ritual. This step is owned by the command, not the agent — human-gate authority lives here.

    Mockups produced. Review them carefully (Figma frames listed above).
Approve to push to engineering, iterate to refine, reject to abort.
> approve / iterate / reject
    • On approve: touch .claude/.design-approved-<scope-slug>. Print: Design approved for <scope>. Engineering may proceed via /frontend-build <scope>.
    • On iterate: write nothing. Print: Iterating. Make changes in Figma (or re-run /ux-wireframe <scope> for contract changes), then re-run /ux-mockup <scope>.
    • On reject: write nothing. Ask the operator for a one-line reason. Print: Mockup rejected: <reason>. No marker written. Re-run /ux-wireframe <scope> with the reason in mind.

Read the full file on GitHub · 42 lines

Changes

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.

  1. 3d ago First seen · 42 lines · 63 tokens per session scan A 720aa9fc605d

Subscribe to this mod's changes

ux-mockup is a command published in the GitHub repository rajconnects/founder-stack (2 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 847 once invoked, about $0.0003 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.

Design and UX
Related

Other commands, from other repositories

ui-flow-review

Review menus, HUD, navigation, and player flow from a UX perspective.

MRCalderon3D/everything-game-dev-code · 15 tokens

template-ui

Design a Sent template-builder interface.

sentdm/sent-plugin · 6 tokens

responsive-design-specialist

Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.

imsaif/design-with-claude · 36 tokens

study

Runtime entry point for extracting design DNA from a live URL, screenshot, or reference site. Part of the Discovery lifecycle phase.

alwkala/tidyfactor-design · 0 tokens

4-generate

Run Stage 4 of the design system skill generation pipeline: parallel skill file generation.

vercel-labs/design-systems-to-agent-skills · 0 tokens

audit-ux

Whole-repo adversarial UX audit of the shipped user surfaces -> docs/audits/ux-audit- .md.

diegomarino/fable-audits · 26 tokens