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 alvin-reyes/better-agentic-ide --skill bmad-uxgit clone --depth 1 https://github.com/alvin-reyes/better-agentic-ideWrote 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/alvin-reyes/better-agentic-ide/bmad-ux)<a href="https://agentmods.dev/skills/alvin-reyes/better-agentic-ide/bmad-ux"><img src="https://agentmods.dev/badge/skills/alvin-reyes/better-agentic-ide/bmad-ux/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/alvin-reyes/better-agentic-ide/bmad-ux"><img src="https://agentmods.dev/badge/skills/alvin-reyes/better-agentic-ide/bmad-ux.svg" alt="Reviewed on agentmods" width="80" 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.00054 | $0.02721 |
| Opus 5.5 | $0.00022 | $0.01088 |
| Sonnet 5.5 | $0.00011 | $0.00544 |
| Haiku 4.5 | $0.00005 | $0.00272 |
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 today.
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 — 96 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 unless a theme is already in place and the user confirms it. 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}.
What ships with it
17 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 1.1 KB
- 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.0 KB
- assets/headless-schemas.md 2.6 KB
- assets/key-screens.md 2.1 KB
- assets/validation-report-template.html 11 KB
- bmod.toml 80 B
- customize.toml 4.5 KB
- references/creative-tools.md 1.9 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.
- today First seen · 96 lines · 54 tokens per session scan A 278ff0c44956
bmad-ux is a skill published in the GitHub repository alvin-reyes/better-agentic-ide (85 stars, last pushed 9d ago), licensed MIT. It adds 54 tokens to every session and 2,721 once invoked, about $0.0002 per session on Opus 5.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-10-26.
Other skills, from other repositories
architecture-diagram
Dark-themed SVG architecture/cloud/infra diagrams as HTML.
concept-diagrams
Minimal SVG diagrams as standalone HTML files.
frontend-design
Create distinctive, production-grade frontend interfaces.
living-ui
Use when building an animated or interactive widget, explainer or dashboard page: how motion feels, where the eye goes, where words sit, reduced motion, keyboard and screen readers. Style-neutral: it never picks colours, fonts or shapes. Pairs with the widgets skill.
theme-pack-authoring
Build, validate, and install Kiro Crew theme packs -- pack anatomy, the 56-variable palette, role-tagged fonts, the overrides.css allowlist (what installs vs what actually renders), and the install-verify cycle. Use when the user wants to create or edit a theme pack.
image-authoring
Author images and diagrams as code — SVG, Pillow, Excalidraw, mermaid. Load when asked to draw, illustrate, or make an image, icon, logo, poster, or diagram.