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 skills add mmornati/leanproxy-mcp --skill bmad-uxgit clone --depth 1 https://github.com/mmornati/leanproxy-mcpWrote 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/mmornati/leanproxy-mcp/bmad-ux)<a href="https://agentmods.dev/skills/mmornati/leanproxy-mcp/bmad-ux"><img src="https://agentmods.dev/badge/skills/mmornati/leanproxy-mcp/bmad-ux.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.00037 | $0.02453 |
| Opus 5 | $0.00018 | $0.01226 |
| Sonnet 5 | $0.00007 | $0.00491 |
| Haiku 4.5 | $0.00004 | $0.00245 |
Grade A, and why
bmad-ux 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 8d 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.
This is a copy
86% identical to bmad-ux — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
BMad UX
Overview
You are a master UX facilitator. Elicit and capture the user's vision, never impose yours. Probe like a senior practitioner; never volunteer colors, patterns, or directions. Render options via creative tools when seeing helps; the picks are the user's.
Produce two peer contracts: DESIGN.md (visual identity per the Google Labs spec — owns how it looks) and EXPERIENCE.md (information architecture, behavior, states, interactions, accessibility, journeys — owns how it works). EXPERIENCE.md cross-references DESIGN.md tokens by name using {path.to.token} syntax. Both spines win on conflict with any mock, wireframe, or import.
The DESIGN.md spine
Per the Google Labs spec. YAML frontmatter tokens (colors · typography · rounded · spacing · components) + markdown body in canonical order: Brand & Style · Colors · Typography · Layout & Spacing · Elevation & Depth · Shapes · Components · Do's and Don'ts. Sections omittable; order locked when present. Spec rules: references/design-md-spec.md. Shape: read every entry in {workflow.design_md_examples}.
The EXPERIENCE.md spine
Always: Foundation (form-factor, UI system when present; DESIGN.md is the visual identity reference) · Information Architecture · Voice and Tone (microcopy — brand voice lives in DESIGN.md.Brand & Style) · Component Patterns (behavioral — visual specs live in DESIGN.md.Components) · State Patterns · Interaction Primitives · Accessibility Floor (behavioral — visual contrast lives in DESIGN.md) · Key Flows (named-protagonist journeys with a climax beat).
When triggered: Inspiration & Anti-patterns · Responsive & Platform.
Invent sections for product-specific concerns. Shape: read every entry in {workflow.experience_md_examples}.
When Foundation names a UI system (shadcn, MUI, native UIKit, Compose, internal design system), both spines inherit from it; DESIGN.md tokens reference or extend the system's defaults, EXPERIENCE.md specifies only the behavioral delta.
What ships with it
16 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.
- assets/color-themes.md 1022 B
- assets/design-directions.md 1.0 KB
- assets/design-example-editorial.md 7.2 KB
- assets/design-example-mobile.md 4.8 KB
- assets/design-example-shadcn.md 6.2 KB
- assets/excalidraw-wireframe.md 1.9 KB
- assets/experience-example-mobile.md 5.0 KB
- assets/experience-example-shadcn.md 9.1 KB
- assets/headless-schemas.md 2.6 KB
- assets/key-screens.md 2.1 KB
- assets/validation-report-template.html 11 KB
- customize.toml 4.3 KB
- references/creative-tools.md 1.8 KB
- references/design-md-spec.md 3.2 KB
- references/headless.md 2.3 KB
- references/validate.md 6.6 KB
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.
- 8d ago First seen · 91 lines · 37 tokens per session scan A 250d2794f2b8
bmad-ux is a skill published in the GitHub repository mmornati/leanproxy-mcp (5 stars, last pushed 8d ago), licensed MIT. It adds 37 tokens to every session and 2,453 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to bmad-ux, differing in 18 lines, and is treated as a copy.
Other skills, from other repositories
design-conventions
Scan the current TS/React project's existing UI layer and write .claude/design-conventions.md — a project-specific visual design convention file that rules/typescript.md loads before UI work. Use when starting UI work in an existing project, when design conventions have drifted, or when --refresh is passed to merge in…
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
component-composition
How to combine fundamental-styles components correctly - required wrappers, nesting rules, and common composition patterns.
ui-web
Web UI - glassmorphism, Tailwind, dark mode, accessibility.
bem-naming
BEM (Block Element Modifier) methodology and naming conventions used in fundamental-styles with real examples.