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 joao-aires/agent-skills-public --skill interface-designgit clone --depth 1 https://github.com/joao-aires/agent-skills-publicWrote 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/joao-aires/agent-skills-public/interface-design)<a href="https://agentmods.dev/skills/joao-aires/agent-skills-public/interface-design"><img src="https://agentmods.dev/badge/skills/joao-aires/agent-skills-public/interface-design/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/joao-aires/agent-skills-public/interface-design"><img src="https://agentmods.dev/badge/skills/joao-aires/agent-skills-public/interface-design.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.00055 | $0.01708 |
| Opus 5.5 | $0.00022 | $0.00683 |
| Sonnet 5.5 | $0.00011 | $0.00342 |
| Haiku 4.5 | $0.00006 | $0.00171 |
Grade A, and why
interface-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 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design and refine the complete interface experience
Own a coherent user-facing experience rather than separate visual, interaction and critique phases. Work from actual user tasks, accepted product decisions, existing application evidence and the requested stopping point. The method applies across web, desktop, browser extensions and native applications; domain specialists contribute application constraints and archetype patterns, and the accepted technical stack owns implementation.
Use this skill to support design, develop, implement, improve and review. Direct requests to design, inspect or critique do not authorize source edits; authorized implementation preserves behavior and existing design commitments. A visual-only improvement should not redesign navigation, and a changed flow should not unnecessarily reopen branding.
Choose the needed depth
| Requested work | Primary focus |
|---|---|
| New product or substantial redesign | User tasks, flows, foundation choices, contextual visual direction and a representative rendered slice |
| Navigation, forms or dialog changes | Destinations, state transitions, focus, error/recovery, drafts and affected callers |
| Visual refinement | Real hierarchy, spacing, typography, color, density, borders, depth, images and accepted tokens |
| Read-only critique | Observed defects, severity, specific surface/state, smallest justified correction and verification gaps |
| Design handoff and implementation | Shared composition, component/state mapping, responsive variants and actual rendered/behavioral checks |
Establish audience, task, content, platform, roles, accepted choices and scope. Before settling a new design, inspect existing project constraints and relevant application-archetype/domain expertise (tasks, objects, data semantics and candidate patterns), platform/technical expertise (native surface, actual component-system behavior, accessibility contracts and feasibility), and accepted product evidence. Those inputs shape the design; they are not downstream implementation details. Select optional specialists by capability and installed descriptions, not a hardcoded catalogue or dependency. Distinguish evidence, hypotheses and reversible proposals. Ask only for material unresolved decisions; do not require a brand-asset hunt or research study for routine UI work.
What ships with it
9 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.
- references/component-and-token-audits.md 1.7 KB
- references/interaction-references.md 1.3 KB
- references/measurement-and-applicability.md 975 B
- references/navigation-and-configuration.md 8.4 KB
- references/ui-foundations.md 3.2 KB
- references/visual-craft.md 4.0 KB
- references/visual-direction.md 6.2 KB
- references/visual-principles.md 5.4 KB
- references/visual-review.md 3.4 KB
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 · 58 lines · 55 tokens per session scan A 6d819f074c8f
interface-design is a skill published in the GitHub repository joao-aires/agent-skills-public (2 stars, last pushed 8d ago), licensed MIT. It adds 55 tokens to every session and 1,708 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-10-28.
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…