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 markerikson/opencode-config-example --skill web-interface-guidelinesgit clone --depth 1 https://github.com/markerikson/opencode-config-exampleWrote 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/markerikson/opencode-config-example/web-interface-guidelines)<a href="https://agentmods.dev/skills/markerikson/opencode-config-example/web-interface-guidelines"><img src="https://agentmods.dev/badge/skills/markerikson/opencode-config-example/web-interface-guidelines/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/markerikson/opencode-config-example/web-interface-guidelines"><img src="https://agentmods.dev/badge/skills/markerikson/opencode-config-example/web-interface-guidelines.svg" alt="Reviewed on agentmods" width="80" 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.00048 | $0.02689 |
| Opus 5.5 | $0.00019 | $0.01076 |
| Sonnet 5.5 | $0.00010 | $0.00538 |
| Haiku 4.5 | $0.00005 | $0.00269 |
Grade A, and why
web-interface-guidelines 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 1mo 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Interface Guidelines
Source: Vercel Web Interface Guidelines — a living, non-exhaustive list of interface design decisions. Most guidelines are framework-agnostic, some specific to React/Next.js.
Interactions
- Keyboard works everywhere. All flows are keyboard-operable & follow the WAI-ARIA Authoring Patterns.
- Clear focus. Every focusable element shows a visible focus ring. Prefer
:focus-visibleover:focusto avoid distracting pointer users. Set:focus-withinfor grouped controls. - Manage focus. Use focus traps, move & return focus according to the WAI-ARIA Patterns.
- Match visual & hit targets. Exception: if the visual target is < 24px, expand its hit target to >= 24px. On mobile, the minimum size is 44px.
- Mobile input size.
<input>font size is >= 16px on mobile to prevent iOS Safari auto-zoom/pan on focus. - Respect zoom. Never disable browser zoom.
- Hydration-safe inputs. Inputs must not lose focus or value after hydration.
- Don't block paste. Never disable paste in
<input>or<textarea>. - Loading buttons. Show a loading indicator & keep the original label.
- Minimum loading-state duration. If you show a spinner/skeleton, add a short show-delay (~150-300 ms) & a minimum visible time (~300-500 ms) to avoid flicker on fast responses. React
<Suspense>does this automatically. - URL as state. Persist state in the URL so share, refresh, Back/Forward navigation work (e.g., nuqs).
- Optimistic updates. Update the UI immediately when success is likely; reconcile on server response. On failure, show an error & roll back or provide Undo.
- Ellipsis for further input & loading states. Menu options that open a follow-up (e.g., "Rename...") & loading/processing states (e.g., "Loading...", "Saving...", "Generating...") end with an ellipsis.
- Confirm destructive actions. Require confirmation or provide Undo with a safe window.
- Prevent double-tap zoom on controls. Set
touch-action: manipulation. - Tap highlight follows design. Set
webkit-tap-highlight-color. - Design forgiving interactions. Controls minimize finickiness with generous hit targets, clear affordances, & predictable interactions (e.g., prediction cones).
- Tooltip timing. Delay the first tooltip in a group; subsequent peers have no delay.
- Overscroll behavior. Set
overscroll-behavior: containintentionally (e.g., in modals/drawers). - Scroll positions persist. Back/Forward restores prior scroll.
- Autofocus for speed. On desktop screens with a single primary input, autofocus. Rarely autofocus on mobile because the keyboard opening can cause layout shift.
- No dead zones. If part of a control looks interactive, it should be interactive.
- Deep-link everything. Filters, tabs, pagination, expanded panels — anytime
useStateis used. - Clean drag interactions. Disable text selection & apply
inertwhile an element is dragged. - Links are links. Use
<a>or<Link>for navigation so standard browser behaviors work (Cmd/Ctrl+Click, middle-click, right-click). Never substitute with<button>or<div>. - Announce async updates. Use polite aria-live for toasts & inline validation.
- Locale-aware keyboard shortcuts. Internationalize keyboard shortcuts for non-QWERTY layouts. Show platform-specific symbols.
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.
- 1mo ago First seen · 137 lines · 48 tokens per session scan A 38249a8bee58
web-interface-guidelines is a skill published in the GitHub repository markerikson/opencode-config-example (48 stars, last pushed 5mo ago), licensed MIT. It adds 48 tokens to every session and 2,689 once invoked, about $0.0002 per session on Opus 5.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
anti-slop-design
Autonomous Principal Design Technologist. Cures vibe-coded software from AI frontend slop using curated token archetypes and 7-axis quality gating.
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…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
open-design-setup
Prepare or repair a project's prototyping environment so open-design can build prototypes with the project's own component library and render them through the project's toolchain. Use when the library target is needed and docs/design/prototyping.md is missing, stale, or failing; excludes HTML-only design work and…
frontend-visual-qa
Audits rendered UI and specific task/object-link handoffs; excludes ordinary source citations alone. Audits already-rendered UI and Markdown/Obsidian image layout — web app, deck/slide, dashboard, design-system, or Electron/native app — via real-browser/native-app journeys and a Playwright sweep. Use after UI…