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/anilcancakir/claude-code-plugin/frontend-designnpx skills add anilcancakir/claude-code-plugin --skill frontend-designgit clone --depth 1 https://github.com/anilcancakir/claude-code-pluginWrote 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/anilcancakir/claude-code-plugin/frontend-design)<a href="https://agentmods.dev/skills/anilcancakir/claude-code-plugin/frontend-design"><img src="https://agentmods.dev/badge/skills/anilcancakir/claude-code-plugin/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 | $0.00028 | $0.03531 |
| Opus 5 | $0.00014 | $0.01766 |
| Sonnet 5 | $0.00006 | $0.00706 |
| Haiku 4.5 | $0.00003 | $0.00353 |
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 4d 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 — 442 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Design
Production-grade UI design skill combining design system thinking with bold aesthetic execution. Covers web (HTML/CSS/JS, React, Vue, etc.) and mobile (Flutter, React Native, SwiftUI, etc.).
MODE DETECTION (FIRST STEP)
Analyze the user's request to determine platform:
| Request Pattern | Mode | Focus |
|---|---|---|
| HTML, CSS, JS, React, Vue, Next.js, landing page, dashboard, web app | WEB |
Browser viewport, responsive breakpoints, CSS animations |
| Flutter, React Native, SwiftUI, Kotlin, mobile app, iOS, Android | MOBILE |
Touch targets, safe areas, platform depth, native patterns |
| Unspecified | WEB |
Default to web unless context suggests mobile |
DESIGN PROCESS (BEFORE CODING)
Before writing any code, commit to a BOLD aesthetic direction by answering four questions:
- Purpose: What problem does this interface solve? Who uses it?
- Tone: Pick a clear direction — brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian. Commit fully.
- Constraints: Technical requirements (framework, performance, accessibility)
- Differentiation: What is the ONE thing someone will remember about this interface?
CRITICAL: Choose a clear conceptual direction and execute with precision. Bold maximalism and refined minimalism both work — the key is intentionality, not intensity.
Then implement working code that is:
- Production-grade and functional
- Visually striking and memorable
- Cohesive with a clear aesthetic point-of-view
- Meticulously refined in every detail
Design-First Workflow
- Design the actual piece of functionality first — not the shell, navigation, or chrome
- Work in grayscale first — add color after hierarchy is clear
- Establish systems (spacing, type, color) before detailed design
- Details come later — work in cycles
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.
- 4d ago First seen · 442 lines · 28 tokens per session scan A fedcc596ae8b
frontend-design is a skill published in the GitHub repository anilcancakir/claude-code-plugin (2 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 3,531 once invoked, about $0.0001 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
spherse-create-agent-chat-theme
Use when creating or editing an agent-level Spherse chat window theme.css for custom chat backgrounds, headers, message bubbles, avatars, composer inputs, markdown blocks, or placeholder text.
accessible-web-animation-builder
Create performant web animations with proper accessibility and timing.
page-style-adaptation
Adapt an existing page, embedded app, iframe, or submodule frontend to match a host application's visual system. Use when Codex is asked to align page background, typography, spacing, borders, radii, shadows, header density, tooltip chrome, responsive/mobile layout, or scroll behavior with an existing product such as…
design-taste-frontend
Senior UI/UX Engineer. Architect digital interfaces overriding default LLM biases. Enforces metric-based rules, strict component architecture, CSS hardware acceleration, and balanced design engineering.
artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
frontend-design
Build distinctive, production-grade frontend interfaces with strong visual identity using compile-free native HTML/CSS/JS by default.