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 soumyachk101/VibeLens --skill responsive-auditgit clone --depth 1 https://github.com/soumyachk101/VibeLensWrote 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/soumyachk101/vibelens/responsive-audit)<a href="https://agentmods.dev/skills/soumyachk101/vibelens/responsive-audit"><img src="https://agentmods.dev/badge/skills/soumyachk101/vibelens/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/soumyachk101/vibelens/responsive-audit"><img src="https://agentmods.dev/badge/skills/soumyachk101/vibelens/responsive-audit.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.00041 | $0.00386 |
| Opus 5 | $0.00020 | $0.00193 |
| Sonnet 5 | $0.00008 | $0.00077 |
| Haiku 4.5 | $0.00004 | $0.00039 |
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 10d 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.
What it actually says
Responsive audit
Target: $ARGUMENTS (if empty, ask for the URL).
Steps
- Capture the same URL three times with
inspect_localhost_ui:viewport: "mobile"(390×844),"tablet"(820×1180),"desktop"(1920×1080). UsefullPage: trueso nothing below the fold is missed. - For each capture, look for the failure modes that only appear at one width:
- horizontal overflow / content escaping its container
- text wrapping into one word per line, or not wrapping at all
- nav or toolbar collapsing incorrectly, or not collapsing at all
- tap targets under ~44px on mobile
- images and grids that do not reflow
- fixed pixel widths that exceed the viewport
- Cross-reference the
simplifiedDOMfrom the mobile capture. Responsive bugs are almost always a missing or wrong breakpoint prefix (md:,lg:) or a hardcoded width. Quote the exact class list you are changing. - Fix the narrowest breakpoint first, then re-capture that viewport to confirm. Only then move up — a mobile fix often resolves tablet too.
- Re-capture all three at the end and report the before/after per viewport.
Notes
- Report only real breakage. Do not restyle a page that already works because you would have designed it differently.
- Mobile and tablet render at deviceScaleFactor 2 with touch emulation, so hover-only interactions are a genuine finding on those viewports.
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.
- 10d ago First seen · 34 lines · 41 tokens per session scan A a8752628f1e6
responsive-audit is a skill published in the GitHub repository soumyachk101/VibeLens (0 stars, last pushed 3d ago), licensed MIT. It adds 41 tokens to every session and 386 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
frontend-ui-engineering
Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
21st-ui
Find, install, and generate UI with 21st.dev. Use when the user asks for a UI component (pricing table, hero, navbar, dashboard, form, etc.), wants design inspiration, needs a brand logo as an SVG component, or wants to generate new UI from a prompt.
ui-designer
Elite UI/UX Design Lead & Frontend Architect. Generates distinctive, non-templated interfaces with opinionated aesthetics, deliberate typography, and exact UX copy. Triggers on UI design, frontend styling, or layout creation.
html-css-responsive
Custom Instructions: HTML5 & CSS3 Responsive Design Expert.
css-architecture
Structure CSS/Tailwind for maintainability — tokens, BEM naming, specificity control, responsive patterns.
frontend-ui-engineering
A set of practices for building polished, accessible, responsive user interfaces and reusable front-end components.