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/markerikson/opencode-config-example/frontend-designnpx skills add markerikson/opencode-config-example --skill frontend-designgit clone --depth 1 https://github.com/markerikson/opencode-config-exampleWhat 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.00046 | $0.01898 |
| Opus 5 | $0.00023 | $0.00949 |
| Sonnet 5 | $0.00009 | $0.00380 |
| Haiku 4.5 | $0.00005 | $0.00190 |
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 2d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adapted from Impeccable by Paul Bakaus (Apache 2.0 license). Modified for dashboard/tool UI: emphasis shifted from bold creative expression to clarity, information density, scanability, and consistent design systems.
This skill guides creation of polished, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with careful attention to design details and intentional choices.
Design Direction
Establish a clear design direction before writing code:
- Purpose: What problem does this interface solve? Who uses it? What data matters most?
- Tone: Choose an appropriate aesthetic — refined minimal, utilitarian, editorial, industrial, soft neutral, etc. Match the tone to the tool's purpose. A trading dashboard and a documentation site need very different treatments.
- Constraints: Technical requirements (framework, performance, accessibility).
- Consistency: Define a design system early — tokens, patterns, component conventions. Reuse relentlessly. Every one-off choice is technical debt.
CRITICAL: Choose a clear direction and execute it with precision. The key is intentionality: every color, spacing value, and typographic choice should trace back to a deliberate decision, not a default.
Then implement working code that is:
- Production-grade and functional
- Visually clear and scannable
- Cohesive with a consistent design system
- Meticulously refined in every detail
Frontend Aesthetics Guidelines
Typography
→ Consult typography reference for scales, pairing, and loading strategies.
Choose fonts appropriate to the interface's purpose. For data-heavy tools, readability and numeric clarity matter more than personality.
DO: Use a modular type scale with fluid sizing (clamp)
DO: Vary font weights and sizes to create clear visual hierarchy
DO: Use font-variant-numeric: tabular-nums for data columns
DON'T: Use overused fonts—Inter, Roboto, Arial, Open Sans, system defaults — unless they genuinely serve the purpose (system fonts are fine for tools)
DON'T: Use monospace typography as lazy shorthand for "technical/developer" vibes
DON'T: Put large icons with rounded corners above every heading—they rarely add value and make sites look templated
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.
- 2d ago First seen · 138 lines · 46 tokens per session scan A e31793ddf4a3
frontend-design is a skill published in the GitHub repository markerikson/opencode-config-example (44 stars, last pushed 3mo ago), licensed MIT. It adds 46 tokens to every session and 1,898 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…