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 jukrap/ai-agent-playbook --skill ui-polishgit clone --depth 1 https://github.com/jukrap/ai-agent-playbookWrote 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/jukrap/ai-agent-playbook/ui-polish)<a href="https://agentmods.dev/skills/jukrap/ai-agent-playbook/ui-polish"><img src="https://agentmods.dev/badge/skills/jukrap/ai-agent-playbook/ui-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/jukrap/ai-agent-playbook/ui-polish"><img src="https://agentmods.dev/badge/skills/jukrap/ai-agent-playbook/ui-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.00024 | $0.00138 |
| Opus 5 | $0.00012 | $0.00069 |
| Sonnet 5 | $0.00005 | $0.00028 |
| Haiku 4.5 | $0.00002 | $0.00014 |
Grade A, and why
ui-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 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.
What it actually says
UI Review and Polish
Inspect the rendered screen and the user's task. Keep existing design-system ownership and deliberate visual choices. A review request produces findings; an authorized edit proceeds directly to the scoped correction.
Consult references/rendered-review.md when the task needs concrete checks or a before/after comparison. A small, clear edit does not require the reference. Static scan signals are candidates, never automatic design defects. Load styling-policy detail only when conventions conflict. Do not chain separate polish, style-selection, and generic-UI skills.
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 Changed · -13 lines · -3 tokens per session 96a20278c7ca
- 10d ago First seen · 24 lines · 27 tokens per session scan A f93859059999
ui-polish is a skill published in the GitHub repository jukrap/ai-agent-playbook (2 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 138 once invoked, about $0.0001 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-ui-engineering
Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
playground
Creates interactive HTML playgrounds — self-contained single-file explorers that let users configure something visually through controls, see a live preview, and copy out a prompt. Use when the user asks to make a playground, explorer, or interactive tool for a topic.
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
baseline-ui
Quickly deslop UI code by fixing spacing, hierarchy, typography, and small layout issues. Use when the interface needs a fast cleanup or polish pass.
web-design-engineer
Build or redesign polished browser-rendered visual artifacts with HTML/CSS/JavaScript/React: pages, dashboards, prototypes, slide decks, animations, UI mockups, and data visualizations. Use for visual front-end creation, design-system exploration, design critique, or explicit browser acceptance / QA of a web artifact.…
frontend-design
A guide for building polished web interfaces such as pages, dashboards, applications, posters, and reusable React or Vue components. It covers visual direction, layout, typography, colors, animation, accessibility, and working HTML, CSS, or JavaScript code.