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.
git clone --depth 1 https://github.com/JuanMarchetto/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/plugins/juanmarchetto/agent-skills/ui-ux-polish)<a href="https://agentmods.dev/plugins/juanmarchetto/agent-skills/ui-ux-polish"><img src="https://agentmods.dev/badge/plugins/juanmarchetto/agent-skills/ui-ux-polish.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
ui-ux-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 4d 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
{
"name": "ui-ux-polish",
"description": "Iterative UI/UX polishing workflow — achieve Stripe-level visual polish through multiple compounding passes",
"version": "1.0.0",
"author": { "name": "Juan Marchetto" },
"homepage": "https://github.com/JuanMarchetto/ui-ux-polish-skill",
"repository": "https://github.com/JuanMarchetto/ui-ux-polish-skill",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 65 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 4d ago First seen · 10 lines scan A 70e6e89bed58
ui-ux-polish is a plugin published in the GitHub repository JuanMarchetto/agent-skills (5 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
html-showcase
Canonical CSS kernel + HTML skeleton for static showcase pages (provenance reports, contractor portfolios, telemetry dashboards). Single design-system SSoT served via jsDelivr CDN; pages stay pure HTML with optional per-page CSS overrides.
ui-design
Craft polished user interfaces with layout grids, color systems, typography scales, responsive patterns, and visual hierarchy.
frontend
Tailwind v4 theming and shadcn/ui component installation, customisation, and recipes.
web-accessibility
Design, build, and review accessible web interfaces with native semantics, keyboard and focus behavior, forms and recovery, responsive input, motion, assistive-technology testing, and WCAG 2.2-informed evidence. Use for a11y, WCAG, ARIA, screen-reader, keyboard, focus, dialog, form, widget, or accessibility review…
frontend-design
Production-grade frontend design skill that avoids AI slop — specific rules for typography, color (OKLCH), layout, motion, interaction, and UX writing.
frontend-developer
Comprehensive frontend development toolkit combining React, accessibility, performance, and responsive design. Includes frontend lead agent for holistic frontend decisions.