Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/komluk/scaffoldingnpx agentmods add skills/komluk/scaffolding/mui-stylingWrote 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/komluk/scaffolding/mui-styling)<a href="https://agentmods.dev/skills/komluk/scaffolding/mui-styling"><img src="https://agentmods.dev/badge/skills/komluk/scaffolding/mui-styling.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.00076 | $0.02679 |
| Opus 5 | $0.00038 | $0.01340 |
| Sonnet 5 | $0.00015 | $0.00536 |
| Haiku 4.5 | $0.00008 | $0.00268 |
Grade A, and why
mui-styling 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 7d 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MUI Styling Skill
Material-UI styling standards and best practices.
When to Apply
- Creating styled components
- Implementing responsive design
- Theme customization
- UI consistency review
Styling Approach Priority
| Priority | Approach | Use When |
|---|---|---|
| 1st | sx prop |
Most styling needs |
| 2nd | styled() API |
Reusable styled components |
| 3rd | Theme overrides | Global component defaults |
| Avoid | Inline CSS / CSS files | Never use in MUI projects |
Spacing System
Spacing Scale
| Value | Pixels | Usage |
|---|---|---|
| 0.5 | 4px | Tight spacing |
| 1 | 8px | Default small |
| 2 | 16px | Default medium |
| 3 | 24px | Section spacing |
| 4 | 32px | Large spacing |
Spacing Props
| Prop | CSS Property |
|---|---|
m |
margin |
p |
padding |
mt, mr, mb, ml |
margin-top/right/bottom/left |
pt, pr, pb, pl |
padding-top/right/bottom/left |
mx, my |
margin x/y axis |
px, py |
padding x/y axis |
gap |
flex/grid gap |
Color System
Theme Colors
| Category | Values |
|---|---|
| Primary | primary.main, primary.light, primary.dark, primary.contrastText |
| Secondary | secondary.main, secondary.light, secondary.dark |
| Status | error.main, warning.main, info.main, success.main |
| Grey | grey.100 through grey.900 |
| Background | background.default, background.paper |
| Text | text.primary, text.secondary, text.disabled |
Color Usage Guidelines
| Use Case | Color |
|---|---|
| Primary actions | primary.main |
| Secondary actions | secondary.main |
| Error states | error.main |
| Success feedback | success.main |
| Backgrounds | background.paper or background.default |
| Body text | text.primary |
| Helper text | text.secondary |
Responsive Design
Breakpoints
| Key | Min Width | Target |
|---|---|---|
xs |
0px | Mobile phones |
sm |
600px | Tablets portrait |
md |
900px | Tablets landscape |
lg |
1200px | Desktops |
xl |
1536px | Large screens |
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.
- 7d ago First seen · 319 lines · 76 tokens per session scan A 8d43de04aa5f
mui-styling is a skill published in the GitHub repository komluk/scaffolding (15 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 2,679 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
interface-craft
Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered product from a generic one. Use this when a screen works but looks unfinished or default, when a layout feels crowded or arbitrary, when a page has no clear focal point, or…
design-system
Builds and maintains the design system a product is assembled from — tokens for color, type, spacing and elevation, component contracts, and the rules that keep them coherent as the product grows. Use this when starting a new interface, when screens have drifted apart visually, when the same component exists three…
interface-redesign
Upgrades an existing interface to a higher standard without rebuilding it — auditing what is there, identifying what reads as generic or unfinished, and sequencing changes by impact. Use this when a product works but looks dated or default, when a redesign is being considered, when deciding whether to restyle or…
frontend-patterns
Context enrichment for frontend UI development using shadcn/ui and Tailwind CSS. Use when building component libraries, implementing UI designs, theming, or working with accessible React components.
fidelity-gate
Build a UI against a frozen visual reference without drift - an inventory extracted before any code, a relics list, and a gate that MEASURES computed styles on a fixture carrying the reference's own data. Use when a mockup, design spec or screenshot is the contract.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", or "vs best practices".