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 2233admin/design-pipeline --skill better-interfacegit clone --depth 1 https://github.com/2233admin/design-pipelineWrote 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/2233admin/design-pipeline/better-interface)<a href="https://agentmods.dev/skills/2233admin/design-pipeline/better-interface"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/better-interface.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.00090 | $0.02772 |
| Opus 5 | $0.00045 | $0.01386 |
| Sonnet 5 | $0.00018 | $0.00554 |
| Haiku 4.5 | $0.00009 | $0.00277 |
Grade A, and why
better-interface 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 3d 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.
This is a copy
91% identical to better-interface — 16 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review the interface as one system
A strong interface is not six independent audits stapled together. Review the whole experience, let each better-* skill own its domain rules, then consolidate the evidence into one prioritized verdict.
This skill owns orchestration only. Accessibility rules belong to better-accessibility; structure to better-layout; copy to better-writing; type to better-typography; color to better-colors; visual polish and motion to better-ui. Never duplicate or override their rules here. Change-scoped review of uncommitted work, branches, and pull requests belongs to interface-review, which resolves the scope and classifies findings before handing the review back here.
Core Principles
1. Resolve Scope and Mode First
Parse the invocation as [quick|full] [scope]. The first token is a mode only when it is exactly quick or full; anything else is part of the scope. Mode defaults to full.
Infer the screen, flow, feature, or repository scope from the request and current workspace. State the resolved scope in the output.
| Mode | Coverage | Finding cap |
|---|---|---|
quick |
The primary path through the scope and the states it actually reaches; report only HIGH and MEDIUM issues |
5 |
full |
Entire requested scope across all six domain skills, including empty, loading, error, and narrow-width states when present | 15 |
If the requested scope is too large to inspect credibly, narrow it to one complete flow: the one the request itself centers on, or failing that the entry path every user of the scope must pass through. State the boundary and what it excluded. Never imply uninspected surfaces were reviewed.
When the request names a branch, pull request, commit range, or uncommitted changes, hand scope resolution to interface-review. It returns the resolved change scope, the affected surfaces, and a status for each finding; severity, consolidation, the cap, the output format, and the verdict stay here, under Change-Scoped Reviews below.
What ships with it
1 file 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.
- 3d ago First seen · 186 lines · 90 tokens per session scan A f3c2fc300a1c
better-interface is a skill published in the GitHub repository 2233admin/design-pipeline (9 stars, last pushed 4d ago), licensed MIT. It adds 90 tokens to every session and 2,772 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to better-interface, differing in 16 lines, and is treated as a copy.
Other skills, from other repositories
ss-lint
Quick automated lint — detects common design system violations in seconds.
ss-learn
Capture a human-approved UI design lesson as a privacy-minimized local StyleSeed candidate, review it, and prepare an opt-in share package without transmitting project code, prompts, screenshots, or brand data. Use when a person asks StyleSeed to remember, learn from, generalize, review, or prepare a reusable rule…
ss-review
Review UI code for design system compliance, accessibility, and best practices.
ss-a11y
Audit a component or page for accessibility issues and fix them.
accessibility-per-component
Run an accessibility audit on a specific design system component. Trigger when someone says: accessibility check, a11y audit, WCAG compliance, is this accessible, check accessibility, does this meet WCAG, screen reader support, keyboard navigation check, or anything about auditing the accessibility of a specific…
component-api-validator
Audit component APIs for consistency, breaking changes, TypeScript coverage, and contract compliance across a component library. Trigger when someone says: component prop review, verify component types are exported, component API audit, check our component interfaces, are our props consistent, API consistency check…