Borrowing it
Nothing to install: this file belongs to ProfSynapse/nexus. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ProfSynapse/nexus/main/.claude/skills/nexus-ui-mockups/SKILL.mdgit clone --depth 1 https://github.com/ProfSynapse/nexusWrote 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/skills/profsynapse/nexus/nexus-ui-mockups)<a href="https://agentmods.dev/skills/profsynapse/nexus/nexus-ui-mockups"><img src="https://agentmods.dev/badge/skills/profsynapse/nexus/nexus-ui-mockups.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.1 | $0.00086 | $0.00638 |
| Opus 5 | $0.00043 | $0.00319 |
| Sonnet 5 | $0.00017 | $0.00128 |
| Haiku 4.5 | $0.00009 | $0.00064 |
Grade A, and why
nexus-ui-mockups 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 6d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nexus UI Mockups
Context: a mockup is a standalone HTML/CSS/JS page in docs/mockups/ that shows
a proposed Nexus surface before the plugin code exists. It is worth building only
if it looks like the real product and promises only what the plugin can actually
render; otherwise it is a drawing that costs a rewrite later. This router points
at the procedures — the detail loads when you take the path.
Workflow
- Decide the artifact. A new or substantially reshaped surface gets a mockup first. A tweak inside an existing layout does not — say so and implement.
- New mockup: follow
protocols/build-mockup.mdstep by step. - Existing mockup to change, supersede, or retire: follow
protocols/revise-mockup.mdfirst — you MUST NOT overwrite a mockup a plan already cites as its visual contract. - Before showing anyone: run
python3 .claude/skills/nexus-ui-mockups/scripts/check_mockup.pyfrom the repo root and fix every error it prints. Nothing else in the repo checks mockups —eslintand the build both ignoredocs/. - Implementation is a separate job under
src/, governed by CLAUDE.md's hard rules and the sibling skills (nexus-mobile-compatfor phone and plugin-store constraints,nexus-agentsfor tools behind the UI,nexus-testingfor proving it in the running plugin). Mockup-only liberties never travel there.
Map
references/fidelity.md— how to make it look like Obsidian and like Nexus: the token block, both themes, production class naming, icons, phone widths.references/honest-mockups.md— keeping the mockup buildable: Obsidian form primitives, labelling simulation, flagging what will not ship as drawn.references/handoff.md— serving it, review, blessing it as a plan's visual contract, and what happens to it after the UI ships.protocols/—build-mockup.md,revise-mockup.md,self-refine.md.scripts/—check_mockup.py(validate a mockup),theme_tokens.py(extract the token set production actually relies on). Run them, do not reimplement.
What ships with it
9 files 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.
- protocols/build-mockup.md 4.3 KB
- protocols/revise-mockup.md 2.8 KB
- protocols/self-refine.md 2.1 KB
- references/fidelity.md 5.6 KB
- references/handoff.md 3.4 KB
- references/honest-mockups.md 4.0 KB
- refinement-log.md 1.5 KB
- scripts/check_mockup.py 8.3 KB runs code
- scripts/theme_tokens.py 4.5 KB runs code
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.
- 6d ago First seen · 42 lines · 86 tokens per session scan A aad718e1b42c
nexus-ui-mockups is a skill published in the GitHub repository ProfSynapse/nexus (154 stars, last pushed 3d ago), licensed MIT. It adds 86 tokens to every session and 638 once invoked, about $0.0004 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-30.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
可点击的功能性 Web 原型, 含导航、英雄区、特性区、CTA.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…
moai-ref-ui-polish
UI polish and interface-completion reference: the small visual details — concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas — that separate polished interfaces from generic ones. Agent-extending skill that amplifies…