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 JohnWayneeee/ai-agent-skills --skill ui-final-polishgit clone --depth 1 https://github.com/JohnWayneeee/ai-agent-skillsWrote 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/johnwayneeee/ai-agent-skills/ui-final-polish)<a href="https://agentmods.dev/skills/johnwayneeee/ai-agent-skills/ui-final-polish"><img src="https://agentmods.dev/badge/skills/johnwayneeee/ai-agent-skills/ui-final-polish/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/johnwayneeee/ai-agent-skills/ui-final-polish"><img src="https://agentmods.dev/badge/skills/johnwayneeee/ai-agent-skills/ui-final-polish.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.00075 | $0.03298 |
| Opus 5 | $0.00037 | $0.01649 |
| Sonnet 5 | $0.00015 | $0.00660 |
| Haiku 4.5 | $0.00007 | $0.00330 |
Grade A, and why
ui-final-polish 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 9d 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Final Polish
Apply a restrained final polish pass to an existing UI component or screen.
Use this skill when the job is to make something feel cleaner, sharper, and more production-ready while preserving the current design. This skill is not a redesign skill.
If the user is asking how to structure, name, organize, package, or hand off a design for code, use pencil-ui-structure first and only use this skill afterward for visual polish.
Short usage name:
ui-final-polish
Goals
- Preserve the existing composition, visual direction, component role, and design intent
- Strengthen text hierarchy
- Improve spacing rhythm and readability
- Fix weak or awkward composition
- Make actions feel properly anchored
- Preserve the existing style unless the user explicitly asks for redesign
Non-Goals
- Do not create a new visual direction
- Do not reinterpret the component's aesthetic
- Do not change the component category, product role, or hierarchy
- Do not broadly retheme colors, materials, effects, typography, or spacing
- Do not apply a style guide as a full redesign unless the user explicitly asks for a redesign
- Do not make changes because they are "more beautiful" if they do not solve a concrete polish issue
- Do not replace a user's preferred design with your preferred design
- Do not silently change multiple unrelated areas when the user named one issue or node
Default Stance
- Polish is a scalpel, not a redesign pass
- Do not redesign when polish is requested
- Keep the current visual language, density, and dark/light mood
- Prefer surgical fixes over broad stylistic changes
- Prefer hierarchy and spacing fixes before introducing new visual elements
- Avoid unnecessary gradients, glows, heavy shadows, or decorative effects unless they improve hierarchy or usability
- Remove friction, not personality
- Polish should improve clarity and confidence without changing the product identity
- If a change would be visible as a new style direction, pause and either avoid it or ask first
- If the user says "do not redesign", treat that as a hard constraint
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.
- 9d ago First seen · 325 lines · 75 tokens per session scan A 16022d6063f0
ui-final-polish is a skill published in the GitHub repository JohnWayneeee/ai-agent-skills (1 stars, last pushed 3mo ago), licensed MIT. It adds 75 tokens to every session and 3,298 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-31.
Other skills, from other repositories
frontend-design
Design and build production-ready frontend interfaces with design systems, responsive layouts, accessible components, and dark mode support. Use when the user requests frontend design or provides relevant inputs for this workflow.
antigravity-design-expert
Core UI/UX engineering skill for building highly interactive, spatial, weightless, and glassmorphism-based web interfaces using GSAP and 3D CSS.
shopify-theme-optimization
Theme speed and UX optimization — Core Web Vitals, Liquid code, image loading, mobile responsiveness.
color-palette-generator
Create an HTML color palette from a mood, description, or image, with swatches, color codes, pairings, and contrast checks. Use for color schemes or brand colors.
slop-eval
Objectively evaluate a UI/web design against the pols.dev anti-slop design law: detect catalogued slop tells with cited evidence, score 8 weighted axes (color, type, components, layout, motion, execution, signature, cohesion), and emit a Slop Report with a 0–100 Slop Index and grade. Use when the user asks to…
brand-visual-language
A brand's visual tone — playful or serious, rounded or angular — should be consistent across all UI elements. Shape language in typography, border-radius, and iconography communicates personality before a single word is read. Use when establishing a design system, choosing icon libraries, setting border-radius tokens…