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 arozumenko/sdlc-skills --skill responsive-auditgit clone --depth 1 https://github.com/arozumenko/sdlc-skillsWrote 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/arozumenko/sdlc-skills/responsive-audit)<a href="https://agentmods.dev/skills/arozumenko/sdlc-skills/responsive-audit"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/responsive-audit/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/arozumenko/sdlc-skills/responsive-audit"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/responsive-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00030 | $0.00540 |
| Opus 5 | $0.00015 | $0.00270 |
| Sonnet 5 | $0.00006 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
responsive-audit 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Responsive Layout Analysis
Responsive 📱 specialist pass — mobile viewport / touch-target / responsive-layout
checks against the real page in a resized browser (not a native app; PWA/hybrid or
plain responsive web only — native iOS/Android is the mobile-testing skill's job).
Data Sources
browser_resize(width: 390, height: 844) # mobile viewport (e.g. iPhone 12/13)
browser_navigate(url) # or re-navigate if already on the page
browser_snapshot() # structure at the mobile viewport
browser_take_screenshot(type:"png", fullPage:true) # visual evidence
browser_resize(width: 1280, height: 800) # always restore a desktop viewport after
Limitation: the factory's Playwright MCP toolset has no browser_evaluate,
so exact touch-target pixel dimensions (getBoundingClientRect) and
window.innerWidth/matchMedia reads are not available. Judge touch-target
size, text legibility, and overlap visually from the mobile screenshot and
snapshot bounding info, and score confidence accordingly (per the evidence
rule in audit-methodology.md) — treat a visually-small target as a lower-
confidence finding than a directly-measured one, and say so.
Focus Areas
- Touch targets that look smaller than ~44x44px (WCAG 2.5.5 — p1)
- Horizontal scrolling (p1)
- Text that looks smaller than ~16px (p2)
- Missing/misconfigured viewport meta (visible as unscaled/zoomed layout — p1)
- Fixed-width layouts breaking at the mobile viewport (p1)
- Hover-only interactions with no visible tap equivalent (p1)
- Wrong mobile keyboard types for input fields (p2)
- Content cut off or overlapping (p1)
- No mobile navigation pattern (hamburger/bottom nav) (p2)
- Non-responsive images (p2)
- Unusable modals on small screens (p1)
Output
Reference element text/role and the screenshot region for touch-target and
layout violations. Always include the mobile screenshot as evidence. Produce
findings in the shared schema — see the qa-auditor audit-methodology.md.
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 · 53 lines · 30 tokens per session scan A a7464d3a1a58
responsive-audit is a skill published in the GitHub repository arozumenko/sdlc-skills (20 stars, last pushed 4d ago), licensed MIT. It adds 30 tokens to every session and 540 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-30.
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…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
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…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
waitlist-page
A simple waitlist page for collecting email addresses from people interested in a new product or early-access release.
tailwindcss
Tailwind CSS v4 conventions — semantic design tokens for theme-safe styling, mobile-first responsive layouts, and v4-first utilities. Use when styling components or writing className utilities with Tailwind. Don't use for plain CSS, CSS-in-JS (styled-components, emotion), or other utility frameworks.