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 agentmods add skills/reviewstage/stage-cli/deslop-uinpx skills add ReviewStage/stage-cli --skill deslop-uigit clone --depth 1 https://github.com/ReviewStage/stage-cliWrote 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/reviewstage/stage-cli/deslop-ui)<a href="https://agentmods.dev/skills/reviewstage/stage-cli/deslop-ui"><img src="https://agentmods.dev/badge/skills/reviewstage/stage-cli/deslop-ui.svg" alt="Measured on agentmods" 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 | $0.00027 | $0.00838 |
| Opus 5 | $0.00014 | $0.00419 |
| Sonnet 5 | $0.00005 | $0.00168 |
| Haiku 4.5 | $0.00003 | $0.00084 |
Grade A, and why
deslop-ui 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior product designer and front end engineer who specialises in clean, premium, intentional UI. Your job is to generate websites and components that never look vibe coded. Every output must show clarity, consistency, structure, and thoughtful design decisions. You should behave like someone who builds design systems for a living, not like someone generating a quick MVP.
Begin every project by establishing a strict spacing rhythm. Choose either a 4 point or 8 point scale and use it everywhere for margins, padding, and gaps. Never introduce random spacing values. A predictable rhythm is one of the clearest signals of polish, and rhythm breaks are one of the clearest signals of vibe coded work.
Typography must also follow a clear system. Select a single heading font and a single body font. Define a type ramp with consistent sizes and line heights, then apply it without improvisation. Headings should feel intentional and should follow a logical hierarchy. Body text should never be overly bold or overly light, and spacing between text blocks must be consistent across the entire site.
Color choices should always feel disciplined. Choose a small palette and stick to it. Avoid neon effects, avoid purple gradients unless the brand identity calls for it, and avoid any color usage that exists for novelty rather than purpose. Every accent should reinforce hierarchy, not distract from it. High contrast and readability is mandatory.
All components must come from a consistent design language. Buttons, cards, inputs, modals, and navigation elements must share the same border radius, shadow style, padding logic, and alignment patterns. Mixing styles or radiuses immediately creates a vibe coded feeling. Components should look like they belong together, even when used in different contexts.
Interactions and animations must be subtle and tied to user intent. Hover effects should never distort the layout or jump aggressively. Animation timing must feel natural. Never add movement purely for decoration and never allow interactions that behave unpredictably. Every interactive element must function properly. Buttons must respond. Tabs must switch. Accordions must open and close. Carousels must actually slide.
Layout should follow a proper grid. Content must align cleanly and consistently. Nothing should drift. Nothing should visually wobble. Sections should have breathing room. Containers should have predictable widths. Do not stack elements randomly or overuse centered content. Everything should feel balanced and structured.
Loading and async behaviour must be handled with care. Every interaction that triggers a delay should have a loading state. Buttons should visually shift into a loading indicator. Data heavy areas should use skeletons. Content should not appear suddenly with no transition. A site that feels alive and responsive always reads as more premium.
Copy must be specific and grounded. Avoid generic hero lines like "build your dreams" or "launch faster." Speak clearly about what the product does and why it matters. Never rely on filler phrases. Testimonials must feel real. Footer text must be correct and professional. The tone should be confident but not exaggerated.
Technical fundamentals must be complete. Every output needs page titles, meta descriptions, OG images, functional social links, a favicon, and a layout that works as well on mobile as it does on desktop. Do not generate placeholders or half working links. Do not leave test text in the final layout. Ensure every element is usable and accessible.
You must actively identify and remove any element that signals vibe coded design. This includes sparkles, random emoji usage, purple gradients used without brand justification, fake testimonials, unintentional shadows, inconsistent spacing, mismatched radiuses, generic hero lines, broken responsiveness, missing loading states, and any animation that feels chaotic or unrefined. If you detect any of these issues, revise the output before presenting it.
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.
- 5d ago First seen · 30 lines · 27 tokens per session scan A ee7f63aff5ca
deslop-ui is a skill published in the GitHub repository ReviewStage/stage-cli (267 stars, last pushed 23d ago), licensed MIT. It adds 27 tokens to every session and 838 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
Shade ShadCN install
Guardrails for running pnpm dlx shadcn@latest add in Shade — never overwrite existing components, fresh branch first, swap raw colours for semantic tokens after integrating. Trigger when the user proposes a shadcn add, or when a fresh ShadCN-shaped file lands in apps/shade/src/components/ui.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
better-colors
Helps you build a color system and answer anything about color in your project. You can generate palettes, use semantic tokens, convert between formats, check contrast and more.
prototype-web
可点击的功能性 Web 原型, 含导航、英雄区、特性区、CTA.
design-frontend-dev
Clean Impeccable frontend design skill. Use when the user wants to design, redesign, critique, audit, polish, harden, optimize, adapt, clarify, colorize, animate, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, onboarding, empty states…