gen-mockup

A tool that creates clickable screen mockups or wireframes from a product brief or PRD. A wireframe is an early layout of an interface; the output can be standalone HTML with Tailwind or real Next.js components.

In plain words
What is it for?
Use it to design desktop or mobile screens at low, medium, or high detail, or generate Next.js screens that can be promoted into an application.
Why use it?
It lets you inspect screens before building the product and keeps them aligned with existing brand files when available. This can expose missing screens or layout problems early.

Command

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/alphaaiservice/cortex/gen-mockup
Clone the repo
git clone --depth 1 https://github.com/alphaaiservice/cortex
Per session 90 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,340 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.00090 $0.01340
Opus 5 $0.00045 $0.00670
Sonnet 5 $0.00018 $0.00268
Haiku 4.5 $0.00009 $0.00134

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

Security

Grade A, and why

gen-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 2d 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.

commands/gen-mockup.md · 91 lines

How it starts

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

UI Mockup Generator — Screens Before You Build

Generate viewable, brand-consistent screen mockups that sit between /gen-prd and /auto-build. The mockup skill auto-loads with this command and defines the quality bar.

$ARGUMENTS = product/screen description, or a path to a PRD/PRD.md.


Section 0: Input Parsing & Context Detection

0a. Parse input

  • If $ARGUMENTS is a file path → read it as the PRD; extract the screen list, primary entities, and user roles.
  • If it's free text → treat it as the product/screen brief.
  • Flags:
    • --fidelity=low|mid|high (default mid)
    • --screens=a,b,c (explicit screen list; otherwise infer from the PRD/brief)
    • --mobile (use a ~390px phone frame instead of desktop)
    • --next (emit real Next.js + shadcn components under mockups-next/ instead of standalone HTML — for direct promotion)

0b. Detect brand source (CRITICAL — reuse, don't invent)

Search the project for, in order:

  1. BRAND_GUIDE.md (from /gen-brand)
  2. globals.css / app/globals.css with OKLCH -- tokens
  3. tailwind.config.* theme extension If found → extract fonts, OKLCH color tokens (light + dark), radius, spacing; use them verbatim. If none found and fidelity is mid/high → tell the user "no brand found — running with a sensible neutral default; run /gen-brand first for on-brand mockups" and proceed with a tasteful default token set.

0c. Decide the screen list

From PRD/brief infer the screens to mock. Map each to one of the 6 Cortex page templates (see frontend skill / CODE_PATTERNS_FRONTEND_PAGES.md): List · Detail · Form · Settings · Dashboard · Auth. Confirm the list back to the user in one line before generating.


Section 1: Generation

1a. Per-screen rules (enforced by the mockup skill)

  • Self-contained: each screen is ONE .html file, openable with no build step. Use Tailwind via CDN (<script src="https://cdn.tailwindcss.com">) for mid/high-fi; plain CSS grayscale for low-fi.
  • Inject the brand tokens into a <style> block as CSS variables; components consume the tokens (never raw hex in markup).
  • Load the brand fonts via <link> (Google Fonts) at mid/high-fi.
  • Realistic content — plausible names, numbers, dates, states. Never lorem ipsum.
  • Show the meaningful states for that screen type (empty / loading skeleton / populated) where it adds signal.
  • Semantic HTML + visible focus states + AA contrast (the accessibility skill applies even here).
  • High-fi screens carry a small fixed "MOCKUP — not production" ribbon.

Read the full file on GitHub · 91 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. 2d ago First seen · 91 lines · 90 tokens per session scan A 3797bff2b39a

Subscribe to this mod's changes

gen-mockup is a command published in the GitHub repository alphaaiservice/cortex (1 stars, last pushed 26d ago), licensed MIT. It adds 90 tokens to every session and 1,340 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.