wireframe-mobile-flow

wireframe-mobile-flow is a skill for Claude Code, Codex from nexu-io/open-design. It costs 141 tokens per session (1,052 once invoked), scanned A, original, Apache-2.0.

A low-detail wireframe showing several phone screens connected in sequence, such as onboarding, a home feed, an item page, and confirmation. It maps how a person moves through a mobile app rather than polishing one screen.

In plain words
What is it for?
Use it to plan onboarding, browsing, item details, checkout, confirmation, and other multi-screen mobile flows.
Why use it?
It makes the steps and transitions in a mobile user journey easy to review before implementation.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to plan onboarding, browsing, item details, checkout, confirmation, and other multi-screen mobile flows.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nexu-io/open-design/wireframe-mobile-flow
About the project

OpenDesign is an open-source, local-first desktop app that lets coding agents create prototypes, dashboards, slide decks, images, video, and design systems as exportable files. It is used by people working with agent runtimes such as Claude Code, Codex, Cursor, and DeepSeek Harness. The catalogue add-ons extend the OpenDesign workflow with skills, instructions, commands, and plugins.

nexu-io/open-design · 94,527 stars · on GitHub · open-design.ai

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.

Any agent
npx skills add nexu-io/open-design --skill wireframe-mobile-flow
Clone the repo
git clone --depth 1 https://github.com/nexu-io/open-design

Made for: Claude Code, Codex.

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 wireframe-mobile-flow

README.md
[![agentmods](https://agentmods.dev/badge/skills/nexu-io/open-design/wireframe-mobile-flow.svg)](https://agentmods.dev/skills/nexu-io/open-design/wireframe-mobile-flow)
Your own site
<a href="https://agentmods.dev/skills/nexu-io/open-design/wireframe-mobile-flow"><img src="https://agentmods.dev/badge/skills/nexu-io/open-design/wireframe-mobile-flow.svg" alt="Measured on agentmods" height="20"></a>
Per session 141 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,052 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Snyk pass 7 Sept 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00141 $0.01052
Opus 5 $0.00071 $0.00526
Sonnet 5 $0.00028 $0.00210
Haiku 4.5 $0.00014 $0.00105

Measured 4d ago against content hash ff02eacc2c75, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

wireframe-mobile-flow 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.

design-templates/wireframe-mobile-flow/SKILL.md · 96 lines

How it starts

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

Wireframe Mobile Flow Skill

Produce a single board showing a mobile app's user flow as a row of lo-fi phone frames. The point is the flow — how a user moves screen to screen — not the polish of any one screen. Keep the screens clean grey-boxes (not scribbly) but keep the connectors and annotations loose and informal.

Workflow

  1. Skip the DESIGN.md if it pushes for finished UI. This skill is deliberately low-fidelity: greyboxes, placeholder rects, and bars stand in for real content. Honor type tokens only loosely (system sans for the board, mono for labels and datelines).
  2. Pick the flow steps from the brief — typically 3–4 connected screens like Onboarding → Home feed → Item detail → Confirm. Name each step so the connector arrows can carry a numbered, verb-first label ("① tap Start", "② open item", "③ add to cart").
  3. Lay out the board, in order:
    • Board header — bold sans title with a pinned "WIREFRAME v0.1 · MOBILE" tag (dashed border, slight rotation) and a mono dateline on the right (date / device / fidelity).
    • Phone row — 3–4 rounded device frames (~240–280px wide) in a horizontal row, each with a notch / status bar. Inside each frame put the greybox content for its step: hero image-placeholder (rect + X), title/price bars, list cards (thumbnail X + 2 text bars), category chips, a bottom tab bar, sticky CTA bars, a confirm checkmark — match the screen's role.
    • Connectors — dashed arrows between consecutive phones, each carrying a small mono step label describing the tap that advances the flow.
    • Annotations — 1–2 small sticky / callout notes pinned near a screen to flag intent ("hero must sell value in 3s", "checkout = 1 screen").
  4. Write a single HTML document:
    • <!doctype html> through </html>, CSS inline, no external JS, no external images (CSS/SVG placeholders only).
    • Use Inter / system-ui for the board and IBM Plex Mono for labels via Google Fonts; a light marker font is allowed for annotations only.
    • Defined dark device-frame borders, medium-grey content blocks on white screens, and a single accent color for arrows and annotations so the board reads clearly even as a small thumbnail.
    • data-od-id on the header, each phone screen, the connectors, and the annotations.
  5. Self-check:
    • The three main phones are visible in a ~1280px viewport; the flow reads left-to-right.
    • Screens are clean greyboxes (not scribbly); connectors and stickies are the loose, informal parts.
    • No near-white-on-white regions — every block has a visible grey fill or border. If a screen renders blank as a thumbnail, raise the contrast.

Read the full file on GitHub · 96 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 4d ago First seen · 96 lines · 141 tokens per session scan A ff02eacc2c75

Subscribe to this mod's changes

wireframe-mobile-flow is a skill published in the GitHub repository nexu-io/open-design (94,527 stars, last pushed yesterday), licensed Apache-2.0. It adds 141 tokens to every session and 1,052 once invoked, about $0.0007 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-09-03.