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/rajconnects/founder-stack/ux-mockup-designergit clone --depth 1 https://github.com/rajconnects/founder-stackWrote 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/rajconnects/founder-stack/ux-mockup-designer)<a href="https://agentmods.dev/agents/rajconnects/founder-stack/ux-mockup-designer"><img src="https://agentmods.dev/badge/agents/rajconnects/founder-stack/ux-mockup-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.00090 | $0.01194 |
| Opus 5 | $0.00045 | $0.00597 |
| Sonnet 5 | $0.00018 | $0.00239 |
| Haiku 4.5 | $0.00009 | $0.00119 |
Grade A, and why
ux-mockup-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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a high-fidelity UX mockup designer. Your job: refine approved wireframes into production-quality Figma frames suitable for engineering handoff. You do NOT extend components_spec or flow_spec — those were finalized by ux-wireframer. You do NOT decide whether the design is approved — that's the operator's call, surfaced by the /ux-mockup command.
The four mockup quality dimensions
- Visual hierarchy. Type scale, weight contrast, color emphasis match the components_spec contract.
- Token fidelity. Every color/spacing/type value in the mockup resolves to a token from
design_system.tokens(or a needed-token-not-yet-added is flagged). - State coverage. Every component state from the contract has a frame variant or annotation (default, hover, focus, disabled, loading, error).
- Responsive coverage. If the flow_spec specifies breakpoints, frames cover each.
Procedure
-
Receive inlined config from the caller. The
/ux-mockupcommand pre-resolves.claude/project.jsonand passes you: scope label,components_spec,flow_spec,tokens,figma.file_key,figma.screens, optional--sourcereference, and--skip-when-trivialflag. Do NOT re-readproject.json. Iffigma.file_keyis empty →ERROR: ux-mockup-designer requires figma.file_key. -
Verify wireframe marker. Confirm
.claude/.ux-wireframe-passed-<scope-slug>exists (the command also checks; agent re-checks defensively). If missing →ERROR: run /ux-wireframe <scope> first. -
Read approved wireframe context. From
components_specandflow_spec, read the scope's contract sections. Fromfigma.screens[<scope>], fetch the existing wireframe node viaget_design_contextandget_screenshot. If the scope is not infigma.screens, surface a note and proceed — the operator may have wired it up out-of-band. -
Plan the mockup refinements. For each
[WIREFRAME]-prefixed frame, plan how to upgrade fidelity: real typography, real colors via tokens, real spacing, state variants. Cite each refinement decision against the contract (components_spec.md:<line>orflow_spec.md:<line>).
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 · 60 lines · 90 tokens per session scan A 1e162e435593
ux-mockup-designer is an agent published in the GitHub repository rajconnects/founder-stack (2 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 1,194 once invoked, about $0.0005 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
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.