anti-ui-slop

anti-ui-slop is a skill for Claude Code from sickn33/agentic-awesome-skills. It costs 39 tokens per session (733 once invoked), scanned A, original, MIT.

A UI design and implementation guide for building interfaces around a product’s real users, content, components, and interaction states. It covers states such as loading, empty, error, success, disabled, and permission screens.

In plain words
What is it for?
It helps design, build, redesign, critique, and review web or iOS screens before release, including responsive behavior and acceptance checks.
Why use it?
It reduces generic interfaces, invented content, and missing states that can make a feature confusing or incomplete. It encourages reuse of the project’s existing design system and conventions.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Codex.

Part of the agentic-awesome-skills plugin — 196 skills shipped together

Good fit It helps design, build, redesign, critique, and review web or iOS screens before release, including responsive behavior and acceptance checks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sickn33/agentic-awesome-skills/anti-ui-slop
About the project

AAS Core is a local control plane for coding agents that lets them search a large catalogue of skills, choose a stack, validate it, and create a reproducible plan. It is used to assemble and review agent workflows through its CLI, local MCP server, catalogue, plugins, and Workbench. The catalogue add-ons provide the skills, plugins, bundles, and workflows that AAS Core helps agents select and validate.

sickn33/agentic-awesome-skills · 46,288 stars · on GitHub · sickn33.github.io

Install

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.

Any agent
npx skills add sickn33/agentic-awesome-skills --skill anti-ui-slop
Clone the repo
git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills

Made for: Claude Code.

Or install agentic-awesome-skills, the plugin that ships this one along with the rest of its 196 skills.

Wrote 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.

agentmods badge for anti-ui-slop

README.md
[![agentmods](https://agentmods.dev/badge/skills/sickn33/agentic-awesome-skills/anti-ui-slop/github.svg)](https://agentmods.dev/skills/sickn33/agentic-awesome-skills/anti-ui-slop)
Your own site
<a href="https://agentmods.dev/skills/sickn33/agentic-awesome-skills/anti-ui-slop"><img src="https://agentmods.dev/badge/skills/sickn33/agentic-awesome-skills/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.

agentmods 80×15 button for anti-ui-slop

Your own site · 80×15
<a href="https://agentmods.dev/skills/sickn33/agentic-awesome-skills/anti-ui-slop"><img src="https://agentmods.dev/badge/skills/sickn33/agentic-awesome-skills/anti-ui-slop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 733 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Snyk warn 7 Sept 2026
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium MCP Rug Pull · line 65
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00039 $0.00733
Opus 5 $0.00019 $0.00367
Sonnet 5 $0.00008 $0.00147
Haiku 4.5 $0.00004 $0.00073

Measured 7d ago against content hash 8ff04df7f8bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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 7d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/agentic-awesome-skills-claude/skills/anti-ui-slop/SKILL.md · 81 lines

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

  1. Identify the screen's real job, primary user and action, required content, and important loading, empty, error, success, disabled, and permission states.
  2. Reuse the repository's components, semantic tokens, typography, spacing, and interaction conventions before adding a new abstraction or visual language.
  3. 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.
  4. 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.

Read the full file on GitHub · 81 lines

Changes

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.

  1. 7d ago First seen · 81 lines · 39 tokens per session scan A 8ff04df7f8bc

Subscribe to this mod's changes

anti-ui-slop is a skill published in the GitHub repository sickn33/agentic-awesome-skills (46,288 stars, last pushed 3d ago), licensed MIT. It adds 39 tokens to every session and 733 once invoked, about $0.0002 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-09-05.