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/fradser/dotclaude/better-interfacenpx skills add FradSer/dotclaude --skill better-interfacegit clone --depth 1 https://github.com/FradSer/dotclaudeWhat 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.00084 | $0.01706 |
| Opus 5 | $0.00042 | $0.00853 |
| Sonnet 5 | $0.00017 | $0.00341 |
| Haiku 4.5 | $0.00008 | $0.00171 |
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 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.
Review the interface as one system
A strong interface is not six independent audits stapled together. Review the whole experience, let each domain reference own its rules, then consolidate the evidence into one prioritized verdict.
This skill owns orchestration only. Accessibility rules belong to references/accessibility/overview.md; structure to references/layout/overview.md; copy to references/writing/overview.md; type to references/typography/overview.md; color to references/colors/overview.md; visual polish and motion to references/ui/overview.md. Never duplicate or override their rules here.
Core Principles
1. Resolve Scope and Mode First
Infer the screen, flow, feature, or repository scope from the request and current workspace. State the resolved scope in the output. Use full when no mode is supplied.
| Mode | Coverage | Finding cap |
|---|---|---|
quick |
Primary user path and highest-traffic states; report only HIGH and MEDIUM issues |
5 |
full |
Entire requested scope across all six domain references, including empty, loading, error, and narrow-width states when present | 15 |
If the requested scope is too large to inspect credibly, narrow it to the highest-traffic complete flow and state the boundary. Never imply uninspected surfaces were reviewed.
2. Recon Before Judgment
Identify the framework, styling system, component library, design tokens, supported viewports, and available preview or test commands. Follow the project's established Tailwind, plain CSS, CSS-in-JS, token, and component conventions.
3. Use Domain References as the Sources of Truth
Before reviewing, read all six domain references below. Load and apply every available reference. In quick mode, inspect all six domains but spend depth only where the primary flow has evidence. In full mode, complete each available domain review before consolidation.
Review in this order so foundational failures are not hidden by polish:
references/accessibility/overview.mdreferences/layout/overview.mdreferences/writing/overview.mdreferences/typography/overview.mdreferences/colors/overview.mdreferences/ui/overview.md
What ships with it
29 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/accessibility/focus-and-keyboard.md 6.4 KB
- references/accessibility/forms.md 3.9 KB
- references/accessibility/hit-areas.md 2.8 KB
- references/accessibility/motion-and-zoom.md 4.0 KB
- references/accessibility/overview.md 8.0 KB
- references/accessibility/screen-readers.md 5.0 KB
- references/accessibility/semantics-and-aria.md 5.2 KB
- references/colors/accessibility-contrast.md 4.2 KB
- references/colors/color-conversion.md 1.8 KB
- references/colors/color-usage.md 4.9 KB
- references/colors/gamut-and-tailwind.md 2.4 KB
- references/colors/overview.md 4.9 KB
- references/colors/palette-generation.md 3.2 KB
- references/layout/grouping-and-alignment.md 5.6 KB
- references/layout/overview.md 5.2 KB
- references/layout/spacing-and-adaptivity.md 6.6 KB
- references/typography/choosing-fonts.md 3.2 KB
- references/typography/css-cheat-sheet.md 3.9 KB
- references/typography/details-and-accessibility.md 4.4 KB
- references/typography/overview.md 12 KB
- references/typography/spacing-and-sizing.md 4.8 KB
- references/typography/variable-fonts-and-opentype.md 4.3 KB
- references/typography/wrapping-and-punctuation.md 3.5 KB
- references/ui/animations.md 13 KB
- references/ui/icons.md 4.3 KB
- references/ui/overview.md 6.4 KB
- references/ui/performance.md 2.9 KB
- references/ui/surfaces.md 6.4 KB
- references/writing/overview.md 6.7 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.
- 2d ago First seen · 138 lines · 84 tokens per session scan A ac8a032c191c
better-interface is a skill published in the GitHub repository FradSer/dotclaude (588 stars, last pushed 21d ago), licensed MIT. It adds 84 tokens to every session and 1,706 once invoked, about $0.0004 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.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.