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 Akakaui/visual-browser-agent --skill responsive-auditgit clone --depth 1 https://github.com/Akakaui/visual-browser-agentWrote 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/akakaui/visual-browser-agent/responsive-audit)<a href="https://agentmods.dev/skills/akakaui/visual-browser-agent/responsive-audit"><img src="https://agentmods.dev/badge/skills/akakaui/visual-browser-agent/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/akakaui/visual-browser-agent/responsive-audit"><img src="https://agentmods.dev/badge/skills/akakaui/visual-browser-agent/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.00026 | $0.00782 |
| Opus 5.5 | $0.00010 | $0.00313 |
| Sonnet 5.5 | $0.00005 | $0.00156 |
| Haiku 4.5 | $0.00003 | $0.00078 |
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 1mo 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Responsive Audit Skill
When to Use
Use this skill to verify responsive design:
- Layout at different breakpoints
- Navigation adaptation (hamburger menu, etc.)
- Content reflow and readability
- Touch target sizes (min 44x44px)
- Image scaling and art direction
- Font scaling and line length
- Horizontal scrolling issues
Instructions
Standard Viewports
Test at minimum:
- Desktop: 1280x720, 1920x1080
- Tablet: 768x1024 (portrait), 1024x768 (landscape)
- Mobile: 375x667 (iPhone), 390x844 (modern), 412x915 (large)
Audit Checklist Per Viewport
Navigation
- Menu accessible (hamburger on mobile)
- Touch targets ≥ 44x44px
- Logo/brand visible
- Search accessible
Content
- No horizontal scroll
- Text readable (min 16px, line length 45-75ch)
- Images scale properly
- Tables handle overflow (scroll/cards)
- Forms usable (inputs sized, labels visible)
Layout
- Grid/flex reflows correctly
- No overlapping elements
- Whitespace appropriate
- Footer accessible
Performance
- Images appropriately sized (srcset)
- No layout shift (CLS)
- Fonts loaded (FOIT/FOUT handled)
Evidence Capture
For each viewport:
navigate(url, waitUntil: "networkidle")capture_screenshot(action: "responsive-{viewport}", requirement: "{viewport} layout")inspect_page(includeA11y: true)- check touch targets, labels
Issue Documentation
{
"viewport": "mobile-375",
"issue": "Navigation menu overlaps content",
"severity": "high",
"evidence": "frames/responsive-mobile-375.png",
"wcag": "1.4.10 Reflow"
}
Output
# Responsive Audit: {url}
## Viewports Tested
- Desktop (1280x720) ✓
- Tablet (768x1024) ✓
- Mobile (375x667) ⚠ Issues found
## Issues
| Viewport | Component | Issue | Severity | Evidence |
|----------|-----------|-------|----------|----------|
| Mobile | Nav | Hamburger menu doesn't close on link click | High | event-012 |
| Tablet | Hero | Text too small (14px) | Medium | event-015 |
## Pass Rate: 85%
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.
- 1mo ago First seen · 115 lines · 26 tokens per session scan A 754459a50610
responsive-audit is a skill published in the GitHub repository Akakaui/visual-browser-agent (0 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 782 once invoked, about $0.0001 per session on Opus 5.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
anti-slop-design
Autonomous Principal Design Technologist. Cures vibe-coded software from AI frontend slop using curated token archetypes and 7-axis quality gating.
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 $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
open-design-setup
Prepare or repair a project's prototyping environment so open-design can build prototypes with the project's own component library and render them through the project's toolchain. Use when the library target is needed and docs/design/prototyping.md is missing, stale, or failing; excludes HTML-only design work and…
frontend-visual-qa
Audits rendered UI and specific task/object-link handoffs; excludes ordinary source citations alone. Audits already-rendered UI and Markdown/Obsidian image layout — web app, deck/slide, dashboard, design-system, or Electron/native app — via real-browser/native-app journeys and a Playwright sweep. Use after UI…
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.