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-layoutmobilegit 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-layoutmobile)<a href="https://agentmods.dev/skills/miqdadbadjuber/anti-slop/antislop-layoutmobile"><img src="https://agentmods.dev/badge/skills/miqdadbadjuber/anti-slop/antislop-layoutmobile/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-layoutmobile"><img src="https://agentmods.dev/badge/skills/miqdadbadjuber/anti-slop/antislop-layoutmobile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00040 | $0.03728 |
| Opus 5.5 | $0.00016 | $0.01491 |
| Sonnet 5.5 | $0.00008 | $0.00746 |
| Haiku 4.5 | $0.00004 | $0.00373 |
Grade A, and why
antislop-layoutmobile 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- antislop-layoutmobile — 91% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
antislop-layoutmobile
Anti Slop: Rules for AI Coding Agents. Mobile Layout skill
Part of the antislop system. Read together with
antislop.md(the core). This skill deep-dives the responsive layout concern: how a layout must reflow across screen sizes, phone to desktop. Breakpoints, scale, grids, overflow, tap targets, and navigation. It references core rules by number and never duplicates or renumbers them. Load it when the task builds or edits a layout that has to hold up at any screen width.
How to use this skill
- Load together with
antislop.mdwhenever the task is mobile or responsive layout work. The core holds the mechanism (the purpose test, the three tiers, the Delivery Gate); this skill holds mobile-layout depth. - Every entry has the same shape: Tell (the pattern), Why (why it reads as slop), Fix (what to do instead), with the governing core rule cited as R-XX.
- The principle behind this skill: mobile layout is a different layout, not the desktop layout at a smaller size. It must reflow: re-stack, rescale, and re-order with intent. Every pattern below is a way a layout fails to reflow.
- The Delivery Gate in the core remains the gate. The "Layoutmobile Skill Checklist" at the end of this file is the mobile-specific supplement to run alongside it.
Breakpoints
Desktop-Only Layout
- Tell: one layout state for every screen; the mobile view is the desktop layout squeezed into a phone.
- Why: R-03 requires a mobile layout that is perfect, not an afterthought. A page that only shrinks has no mobile design at all: cards that worked side by side overlap, and text meant for a wide canvas crowds into a narrow one.
- Fix: define a real mobile state at the breakpoint where the content stops working. The mobile layout reflows: columns stack, sizes drop, and order changes where the content needs it. If the mobile view is just the desktop view at a smaller width, the layout is not done.
Breakpoint Driven by Device List
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.
- 1mo ago Changed · +7 lines · +4 tokens per session 8613395a5109
- 2mo ago First seen · 164 lines · 36 tokens per session scan A 794c5203ea63
antislop-layoutmobile is a skill published in the GitHub repository miqdadbadjuber/anti-slop (7,562 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 3,728 once invoked, about $0.0002 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-system-patterns
Token architecture, component design, naming conventions, theming, and scaling design systems that people actually use.
accessibility-deep-patterns
Advanced accessibility patterns including ARIA, screen reader optimization, cognitive accessibility, and motor impairment design.
animation-choreography
Page transition choreography, staggered animations, and orchestrated motion sequences.
border-craft
Border design patterns, dividers, separators, and using borders as primary design elements.