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/on-deck-society/love-stack/responsive-designnpx skills add on-deck-society/love-stack --skill responsive-designgit clone --depth 1 https://github.com/on-deck-society/love-stackWrote 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/on-deck-society/love-stack/responsive-design)<a href="https://agentmods.dev/skills/on-deck-society/love-stack/responsive-design"><img src="https://agentmods.dev/badge/skills/on-deck-society/love-stack/responsive-design.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.00034 | $0.00597 |
| Opus 5 | $0.00017 | $0.00298 |
| Sonnet 5 | $0.00007 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
responsive-design 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 4d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Responsive Design
When activated, review the user's UI code and CSS for responsive design quality. Focus on the places most commonly broken.
The Review Checklist
-
Viewport meta tag: Confirm the HTML head has
<meta name="viewport" content="width=device-width, initial-scale=1">. Flag if missing or configured to prevent user scaling. -
Breakpoint strategy: Identify the project's breakpoints (via Tailwind config, media queries, or CSS variables). Flag if breakpoints are inconsistent across files or if mobile-first is not the default.
-
Touch targets on mobile: Interactive elements (buttons, links, form inputs) should be at least 44x44 CSS pixels on mobile per WCAG 2.2 AA. Flag elements smaller than this on mobile breakpoints.
-
Font sizes on mobile: Body text should be at least 16px on mobile to prevent iOS zoom-on-focus. Flag smaller font sizes on inputs and readable content.
-
Horizontal scroll: Search for CSS that could cause horizontal overflow on mobile (fixed widths larger than viewport, non-responsive images, tables without overflow handling). Flag each.
-
Grid and flex wrapping: Verify multi-column layouts collapse gracefully on narrow viewports. Flag grids that don't wrap and flex containers with items that overflow.
-
Image responsiveness: Check that images use responsive patterns (srcset, sizes, max-width: 100%, object-fit). Flag images with fixed pixel widths.
-
Mobile-specific UI patterns: Verify mobile users have appropriate patterns (hamburger or bottom nav, full-screen modals instead of desktop modals, swipe gestures where expected). Flag desktop-only interactions that don't have mobile equivalents.
-
Orientation handling: If the app supports landscape, verify layouts don't break at landscape aspect ratios on phones.
-
Safe areas on notched devices: For apps that go edge-to-edge, verify CSS env() safe-area-inset usage on iOS notched devices.
Output Format
Produce a report with:
- Pass/Fail/Partial per check
- Specific file and line references
- Severity (Critical for anything that makes the app unusable on mobile, High for anything that causes visible breakage, Medium for UX polish, Low for best-practice improvements)
- One-line recommended fix per finding
What ships with it
1 file 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.
- 4d ago First seen · 46 lines · 34 tokens per session scan A d7d04d937915
responsive-design is a skill published in the GitHub repository on-deck-society/love-stack (5 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 597 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-08-31.
Other skills, from other repositories
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…
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.
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…
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
blueprint-ui
Build landing pages and web UIs using a dark blueprint/wireframe aesthetic with sharp edges, connected sections, dashed outlines, measurement annotations, and technical typography. Use when creating marketing sites, landing pages, or product pages.
ui-design
UI 样式修改协作流程（已有界面的视觉层微调）。触发硬条件：页面已经在代码里跑着，改的只是它的视觉表现——布局、间距、颜色、字号、圆角、组件搭配。通过"读代码 + ASCII 画出现状让用户确认 → 给 2-3 个 ASCII 方案 → 用户选定 → 最小改动 → 微调"的流程，减少沟通偏差、避免浪费 token。产出：只动样式的代码 diff。硬边界：不动业务逻辑、不动数据流、不改交互行为、不顺手重构。不适用于：界面还不存在、要从零探索长什么样（用 design-exploration）、改的是功能或交互逻辑而不只是视觉（用 req-change-workflow）、照着设计图/截图复刻整页（用…