anti-slop is a set of rules and skills that coding agents use to avoid generic AI-generated interfaces, copy, and code. It is intended for people building pages or writing and reviewing text with an agent, while a user-provided DESIGN.md supplies the visual direction. The catalogue entries package these rules as agent skills and a plugin.
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 miqdadbadjuber/anti-slop --skill antislop-humangit clone --depth 1 https://github.com/miqdadbadjuber/anti-slopWrote 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/miqdadbadjuber/anti-slop/antislop-human)<a href="https://agentmods.dev/skills/miqdadbadjuber/anti-slop/antislop-human"><img src="https://agentmods.dev/badge/skills/miqdadbadjuber/anti-slop/antislop-human/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/miqdadbadjuber/anti-slop/antislop-human"><img src="https://agentmods.dev/badge/skills/miqdadbadjuber/anti-slop/antislop-human.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
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 Excessive Agency · line 25 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00035 | $0.03955 |
| Opus 5.5 | $0.00014 | $0.01582 |
| Sonnet 5.5 | $0.00007 | $0.00791 |
| Haiku 4.5 | $0.00003 | $0.00396 |
Grade A, and why
antislop-human 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- antislop-human — 100% identical, 61 lines differ
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
antislop-human
Anti Slop: Rules for AI Coding Agents. Human skill
Part of the antislop system. Read together with
antislop.md(the core). This skill deep-dives the human concern: the UI must stay usable by people with different eyes, hands, and setups. Contrast, keyboard, focus, states, and the mobile details that exclude people.
How to use this skill
- Load together with
antislop.mdwhenever the task builds or edits UI. The core holds the mechanism (the purpose test, the three tiers, the Delivery Gate); this skill holds the human-side depth: the parts of a UI that exclude people with different eyes, hands, and setups. - Every entry has the same shape: Tell (the pattern), Why (who it excludes, and why it reads as unfinished), Fix (what to do instead), with the governing core rule cited as R-XX.
- Accessibility is not a checklist of extras bolted on at the end. It is part of the core promise that "the UI holds up" (C-4). The Delivery Gate in the core remains the gate; the "Human Skill Checklist" at the end of this file is the supplement to run alongside it.
- The contrast checker (formula + reference table + script) lives in this skill. Use it for every color pairing you cannot verify by eye.
- This skill keeps only the mobile details that exclude people: zooming, and the on-screen keyboard.
Color & Contrast
Low-Contrast Text
- Tell: light grey text on a white or near-white background, thin body text, muted labels chosen because they look "elegant" but are hard to read.
- Why: it excludes low-vision users and everyone in bright light. It is a visual choice made without checking the standard, which is exactly the kind of default the filter exists to catch.
- Fix: meet WCAG AA minimums (R-25): 4.5:1 for normal text, 3:1 for large text (18px+). Compute the ratio; do not eyeball it.
Text Over a Photo or Gradient
- Tell: white text placed directly over an image or gradient that is light in some areas, checked at one bright spot only.
- Why: contrast is local. Where the image is light, the text drops below 4.5:1 even if the hero still "looks" fine. R-25 requires testing the whole area the text passes over, not a single point.
- Fix: add a scrim or a solid color block behind the text, then verify the worst spot, not the best. If any part of the text area fails, the treatment fails.
What ships with it
5 files 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.
- yesterday Changed · +54 lines · +4 tokens per session 49421878e0c0
- 13d ago Changed · +3 lines cfa37d69600e
- 2mo ago First seen · 148 lines · 31 tokens per session scan A 5bc7c8e56cc7
antislop-human is a skill published in the GitHub repository miqdadbadjuber/anti-slop (7,562 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 3,955 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
role-ui-ux-designer
Use when orchestrating UI/UX design systems, anti-AI-slop frontend styling, tactile micro-interactions, responsive design tokens, accessibility standards, and high-fidelity interface engineering.
taste
Anti-slop frontend engineering directive and design taste system. Enforces brief inference, dynamic design dials, absolute prohibition of AI visual tells, and 100% full-output completion.
design-economics
Measuring design ROI, building business cases for design investment, and connecting design metrics to business outcomes.
design-system-patterns
Token architecture, component design, naming conventions, theming, and scaling design systems that people actually use.
competitive-teardown
Structured analysis of competing products covering UX patterns, design quality, positioning, and strategic differentiation opportunities.
design-spec-writing
Writing design specifications that engineers actually read, reference, and build from accurately.