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 agentmods add skills/kouroshez/coding-os/frontend-designnpx skills add kouroshez/coding-os --skill frontend-designgit clone --depth 1 https://github.com/kouroshez/coding-osWrote 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/kouroshez/coding-os/frontend-design)<a href="https://agentmods.dev/skills/kouroshez/coding-os/frontend-design"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/frontend-design.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.00157 | $0.01156 |
| Opus 5 | $0.00078 | $0.00578 |
| Sonnet 5 | $0.00031 | $0.00231 |
| Haiku 4.5 | $0.00016 | $0.00116 |
Grade A, and why
frontend-design 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 5d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Design
Good design looks intentional — every spacing value, type size, and color is a decision, not a default. This skill is the aesthetic direction, and it is framework-independent: the same principles apply whether you write React, Vue, Svelte, React Native, or hand-written HTML/CSS. The implementation patterns are owned by frontend-fundamentals; accessibility by a11y — load all three for real UI work (aesthetic without a11y is a lawsuit; aesthetic without patterns is tech debt).
Check a color pair against WCAG contrast (design + a11y in one):
python3 scripts/check_contrast.py "#1a1a1a" "#ffffff"
Avoid "AI slop" — the generic look
The default generic interface: even gray borders everywhere, centered everything, one font weight, purple-to-blue gradients, emoji as iconography, no hierarchy. It reads as "no decisions were made". Distinctive design makes deliberate choices: a real type scale, intentional asymmetry, a restrained palette with one accent, generous or deliberately tight spacing — consistently applied.
The principles (framework-agnostic)
- Hierarchy — the eye should land on the most important thing first. Achieve it with size, weight, color, and space — not by making everything bold.
- Spacing rhythm — use a scale (4/8px base: 4, 8, 12, 16, 24, 32, 48, 64), never arbitrary values. Consistent spacing is most of what "looks polished" is.
- Typography — a type scale (not 14 random sizes); limited weights; line-height ~1.5 for body, tighter for headings; measure (line length) ~45–75 characters.
- Color — a small palette: a neutral ramp + one or two accents. Define
semantic roles (surface, text, primary, danger), not raw hex scattered in code.
Every text/background pair must pass contrast —
check_contrast.py. - Layout — align to a grid; respect proximity (related things close, unrelated apart); use whitespace as a tool, not filler.
What ships with it
3 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.
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.
- 5d ago First seen · 77 lines · 157 tokens per session scan A 4db595a0bd9b
frontend-design is a skill published in the GitHub repository kouroshez/coding-os (6 stars, last pushed 5d ago), licensed Apache-2.0. It adds 157 tokens to every session and 1,156 once invoked, about $0.0008 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-31.
Other skills, from other repositories
responsive-sweep
Live-verify layout across tablet, laptop, and wide breakpoints by measuring rects, elementFromPoint occlusion, bottom-tab reserve, and screenshots.
maestro-impeccable
Use when designing, reviewing, refining, fixing, or codifying frontend UI with Maestro's self-contained Impeccable core.
terminal-simulation
Generate interactive, animated, responsive HTML-based terminal simulators to showcase CLI commands, scripts, pipelines, or interactive workflows. Use this whenever you need to visually showcase a command line sequence, mock interactive CLI tools, or simulate code executions.
senior-frontend
Build modern, performant frontend applications. Use when developing React/Next.js components, optimizing frontend performance, implementing UI/UX designs, managing state, or reviewing frontend code. Covers React, Next.js, TypeScript, and Tailwind CSS.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…
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…