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 Notysoty/openagentskills --skill responsive-layout-reviewergit clone --depth 1 https://github.com/Notysoty/openagentskillsWrote 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/notysoty/openagentskills/responsive-layout-reviewer)<a href="https://agentmods.dev/skills/notysoty/openagentskills/responsive-layout-reviewer"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/responsive-layout-reviewer/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/notysoty/openagentskills/responsive-layout-reviewer"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/responsive-layout-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00025 | $0.01757 |
| Opus 5 | $0.00013 | $0.00879 |
| Sonnet 5 | $0.00005 | $0.00351 |
| Haiku 4.5 | $0.00003 | $0.00176 |
Grade A, and why
Responsive Layout Reviewer 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 9d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Responsive Layout Reviewer
What this skill does
This skill reviews HTML/CSS, Tailwind, or React component code for responsive design issues. It checks for layout problems at mobile (320–480px), tablet (768–1024px), and desktop (1280px+) breakpoints, identifies common mistakes like fixed widths, missing overflow handling, inaccessible touch targets, and viewport-breaking elements, and produces a specific list of issues with exact fixes for each.
Use this during code review, before shipping a new component or page, or when a layout is broken on certain screen sizes and you need a systematic diagnosis.
How to use
Claude Code / Cline
Copy this file to .agents/skills/responsive-layout-reviewer/SKILL.md in your project root.
Then ask:
- "Use the Responsive Layout Reviewer skill on
src/components/ProductCard.tsx." - "Review this CSS for responsive issues using the Responsive Layout Reviewer skill."
Provide the component file or the HTML/CSS to review.
Cursor
Add the instructions below to your .cursorrules or paste them into the Cursor AI pane before sharing the code to review.
Codex
Paste the HTML/CSS or component code and ask Codex to follow the instructions below.
The Prompt / Instructions for the Agent
When asked to review for responsive design issues, check every item in this checklist:
Breakpoints to evaluate
Unless the project uses a custom breakpoint system, evaluate at:
- Mobile: 320px (small phone), 375px (iPhone standard)
- Mobile landscape: 667px
- Tablet: 768px, 1024px
- Desktop: 1280px, 1440px
- Wide: 1920px
Note the breakpoint system used by the project (Tailwind defaults, Bootstrap, custom media queries) and use those values.
Checklist
Fixed widths
- Any element with a hardcoded pixel width that could overflow on smaller screens (e.g.,
width: 600pxwithoutmax-width: 100%) - Flex or grid children with
flex: 0 0 [fixed]that could overflow - Tables without
overflow-x: autoon a wrapper
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.
- 9d ago First seen · 180 lines · 25 tokens per session scan A 091f02cc8803
Responsive Layout Reviewer is a skill published in the GitHub repository Notysoty/openagentskills (9 stars, last pushed 26d ago), licensed MIT. It adds 25 tokens to every session and 1,757 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-31.
Other skills, from other repositories
frontend-design
Use this skill when specifying, designing, or documenting UI components, layouts, and design systems for frontend implementation. Trigger phrases: 'design this UI component', 'create a responsive layout', 'spec the CSS for', 'design system for'. Do NOT use for backend development, server-side logic, data engineering…
interaction-skill
Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…
layout-skill
Layer A layout-mechanics reference. Stacks on any style skill when the screen is an app shell, dashboard, settings, list-detail, mail/inbox, or any layout with fixed regions plus a scrolling body — or when a layout breaks under long, empty, or unbroken content. Owns spatial structure and scroll ownership; owns zero…
absolute-ui
Build polished, intentional UIs with concrete CSS/Tailwind values — typography, color, layout, spacing, dark mode, accessibility, animations, components. Encodes specific, opinionated rules with exact values, not vague advice. Covers buttons, cards, forms, tables, navigation, dashboards, landing pages, onboarding, and…
accessibility-audit
Conduct accessibility audits against WCAG 2.2 guidelines. Evaluate pages, components, and flows for conformance at A, AA, and AAA levels. Identify issues, assess severity, provide code fixes, and generate audit reports. Covers automated testing, manual testing, keyboard navigation, screen reader compatibility, color…
enhance-web-ui
Polish an existing page's hierarchy, spacing, type, and visual personality. Use when "make this page polished/premium", "less crowded", or "better visual hierarchy". Understood / CPL → enhance-readability. Flow/IA → enhance-web-ux. Breakpoints → audit-responsive.