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 lingxling/awesome-skills-cn --skill anti-ui-slopgit clone --depth 1 https://github.com/lingxling/awesome-skills-cnWrote 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/lingxling/awesome-skills-cn/anti-ui-slop)<a href="https://agentmods.dev/skills/lingxling/awesome-skills-cn/anti-ui-slop"><img src="https://agentmods.dev/badge/skills/lingxling/awesome-skills-cn/anti-ui-slop/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/lingxling/awesome-skills-cn/anti-ui-slop"><img src="https://agentmods.dev/badge/skills/lingxling/awesome-skills-cn/anti-ui-slop.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.00039 | $0.00733 |
| Opus 5.5 | $0.00016 | $0.00293 |
| Sonnet 5.5 | $0.00008 | $0.00147 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
anti-ui-slop 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 10d 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
100% identical to anti-ui-slop — 0 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stop Making UI Slop
Build product-specific UI with 800,000+ real web and iOS screens via UIZZE.
Overview
Use the product brief, existing interface, components, and local design system before reaching for outside references. UIZZE evidence is optional: it should answer a concrete visual question, not turn every interface task into a research project.
When to Use
Use this skill when designing, implementing, redesigning, critiquing, or doing a pre-ship review of a web or iOS interface.
Work From the Product
- Identify the screen's real job, primary user and action, required content, and important loading, empty, error, success, disabled, and permission states.
- Reuse the repository's components, semantic tokens, typography, spacing, and interaction conventions before adding a new abstraction or visual language.
- For a new interface or major redesign, write a short design contract covering hierarchy, workflow shape, allowed components, required states, responsive behavior, and observable acceptance criteria. Keep smaller changes smaller.
- Use product-specific labels and data. Do not invent metrics, activity, testimonials, users, or placeholder workflows to make a layout look complete.
Optional UIZZE Evidence
The free skill and public catalogue work without an account, token, dependency, script, or executable. If a concrete unresolved visual question would benefit from evidence, use the smallest relevant set of screens or materials.
The optional authenticated UIZZE MCP exposes exactly find_ui_references and
find_ui_materials. Use it only when those tools are actually available. If a
search returns nothing, continue silently from repository evidence. Never claim
an MCP-backed result that was not returned by the host.
Treat references as evidence, not templates. Transfer useful decisions about hierarchy, density, navigation, controls, responsive behavior, and state handling; never copy another product's branding, proprietary text, imagery, or exact layout.
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.
- 10d ago First seen · 81 lines · 39 tokens per session scan A 8ff04df7f8bc
anti-ui-slop is a skill published in the GitHub repository lingxling/awesome-skills-cn (312 stars, last pushed 10d ago), licensed MIT. It adds 39 tokens to every session and 733 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to anti-ui-slop, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
anti-ui-slop
Stop coding agents from shipping generic UI. Extend the product's design system, use UIZZE evidence only when useful, cover required states, and inspect the rendered result.
frontend-aesthetic-direction
A skill for choosing a complete visual direction for a new frontend project with no existing brand or design system. It defines rules for typography, colors, spacing, shapes, components, imagery, icons, and motion.
make-tweakable
A hidden floating settings panel for a single-file HTML design or prototype. It lets someone adjust selected colors, fonts, spacing, text, layout options, or feature switches while comparing variations in the same file.
anti-ui-slop
Stop coding agents from shipping generic UI. Extend the product's design system, use UIZZE evidence only when useful, cover required states, and inspect the rendered result.
popular-web-designs
54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.
interaction-skill
Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…