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 mofirojean/angular-ui-skills --skill ui-craftgit clone --depth 1 https://github.com/mofirojean/angular-ui-skillsWrote 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/mofirojean/angular-ui-skills/ui-craft)<a href="https://agentmods.dev/skills/mofirojean/angular-ui-skills/ui-craft"><img src="https://agentmods.dev/badge/skills/mofirojean/angular-ui-skills/ui-craft.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.00207 | $0.01696 |
| Opus 5 | $0.00103 | $0.00848 |
| Sonnet 5 | $0.00041 | $0.00339 |
| Haiku 4.5 | $0.00021 | $0.00170 |
Grade A, and why
ui-craft 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Craft
Cross-cutting skill. Pair this with one of the library-specific skills (
spartan-ng-developer,primeng-developer,ng-zorro-developer,angular-material-developer) plus the baseangular-developer. This skill teaches what good looks like and why. The library skill teaches which component to reach for. Both load together when the user wants polished UI.
When this skill should fire
Activate eagerly when the user says any of:
- "Make this look better / cleaner / more polished"
- "This feels generic" / "looks like a template"
- "Improve the dashboard" / "redesign this page"
- "Why does this look amateur"
- Specific topics: "hierarchy", "spacing", "typography", "color palette", "shadows", "empty state", "tooltip", "hover state", "loading state"
Also activate proactively (without being asked) when you see:
- A dashboard or data-heavy surface being built
- A table with all-grey text, no alignment, no muted/active distinction
- Form labels in the same weight and color as the values
- Color used as the only signal (no icon, no text, no shape backup)
- Hover-only actions with no affordance hinting at them
- Zero empty states / zero loading states for an async surface
The three tells of an amateur dashboard
These are the patterns that immediately give away a UI built without intent. Each gets its own reference file because each is a discipline, not a single rule.
-
Data drives the UI. Not the other way around. The shape, density, alignment, color, and chart-vs-table choice all come from the data being displayed, not from a default table template. Read data-driven-ui.md.
-
Progressive disclosure. Most actions, controls, and metadata don't belong permanently on screen. They belong tucked behind hover, popover, sheet, or context menu, with a clear affordance. The "spectrum of explicitness" runs from always-visible global actions to on-hover row actions to right-click-revealed power-user actions. Read progressive-disclosure.md.
What ships with it
11 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.
- references/color.md 7.1 KB
- references/dashboard-patterns.md 10 KB
- references/data-driven-ui.md 6.3 KB
- references/depth.md 6.0 KB
- references/finishing.md 7.3 KB
- references/hidden-ui.md 7.3 KB
- references/hierarchy.md 6.0 KB
- references/library-bridge.md 8.3 KB
- references/progressive-disclosure.md 6.0 KB
- references/spacing.md 6.5 KB
- references/typography.md 6.8 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 · 83 lines · 207 tokens per session scan A 66c0af82b1f4
ui-craft is a skill published in the GitHub repository mofirojean/angular-ui-skills (29 stars, last pushed 1mo ago), licensed MIT. It adds 207 tokens to every session and 1,696 once invoked, about $0.0010 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
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.
visual-plan
Turn ordinary text plans into rich interactive visual plans with diagrams, file maps, annotated code, open questions, and UI/prototype review when useful.
visual-edit
Open a running local app in Design overview mode as URL-backed iframe screens for visual editing, flow review, duplication, and route-state exploration. Use when the user asks to inspect, compare, or edit a real local app visually in Design.
display-glasses-with-jetpack-compose-glimmer
Provides guidelines for developing projected Android XR apps for display glasses using the Jetpack Compose Glimmer UI toolkit. This skill covers foundational Glimmer design principles, workflows for implementing Jetpack Compose Glimmer, and interaction models for the glasses form factor. Use this skill to build an…
baseline-ui
Quickly deslop UI code by fixing spacing, hierarchy, typography, and small layout issues. Use when the interface needs a fast cleanup or polish pass.
accessibility
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".