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 website-studygit 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/website-study)<a href="https://agentmods.dev/skills/akakaui/visual-browser-agent/website-study"><img src="https://agentmods.dev/badge/skills/akakaui/visual-browser-agent/website-study/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/website-study"><img src="https://agentmods.dev/badge/skills/akakaui/visual-browser-agent/website-study.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.00038 | $0.00994 |
| Opus 5.5 | $0.00015 | $0.00398 |
| Sonnet 5.5 | $0.00008 | $0.00199 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
website-study 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Website Study Skill
When to Use
Use this skill when the user wants to analyze a public website's:
- Visual design (typography, colors, spacing, layout)
- Interactions (hover states, clicks, transitions)
- Responsiveness (breakpoints, mobile/desktop)
- Motion/animations
- Information architecture
- Accessibility
Instructions
Phase 1: Planning
- Clarify scope: Which pages? Which viewports? What aspects matter most?
- Create run context with
createRunContext(goal, requirements) - Define viewports (default: desktop 1280x720, tablet 768x1024, mobile 375x667)
Phase 2: Structured Inspection
For each page and viewport:
navigate(url, waitUntil: "networkidle")inspect_page(includeA11y: true, includeDOM: false)- get accessibility treecapture_screenshot(action: "viewport-{name}", requirement: "{name} layout")- Extract: colors, fonts, spacing, component inventory
Phase 3: Interaction Study
For key interactive elements:
- Identify interactive elements from accessibility tree
- For each: hover, click, focus states
record_interactionfor transitions/animationscapture_screenshotfor each state
Phase 4: Responsive Audit
Use responsive_audit workflow tool or manual:
- Test each viewport breakpoint
- Check: navigation, content reflow, touch targets, readability
- Document issues with screenshots
Phase 5: Animation Study
Use animation_study workflow tool or manual:
- Identify animated elements
- Trigger animations (hover, click, scroll, load)
record_interactionwith 8-second clips- Analyze: easing, duration, purpose, performance
Phase 6: Vision Review
For each captured artifact:
review_visual_evidence(artifacts, requirement, context)- Document findings, confidence, pass/fail
- Build evidence manifest
Phase 7: Synthesis
- Compile findings into structured report
- Include: design system analysis, interaction patterns, responsive issues, animation quality
- Reference all evidence with event IDs
- Save as artifact (Markdown/HTML)
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 · 135 lines · 38 tokens per session scan A ca4816590dbb
website-study is a skill published in the GitHub repository Akakaui/visual-browser-agent (0 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 994 once invoked, about $0.0002 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
webui-code
Use this skill when generating or reviewing WebUI code. This skill contains knowledge on WebUI code following Chrome's Lit-element architecture and styling guidelines.
browserwing-executor
Control browser automation through HTTP API. Supports page navigation, element interaction (click, type, select), data extraction, accessibility snapshot analysis, screenshot, JavaScript execution, and batch operations.
figma-design-review
Critique and review Figma designs to ensure alignment with Chromium codebase components, tokens, and structure. Use when the user asks to critique, review, or audit a design, check alignment with code, or compare a Figma node against component specifications or coding standards.
figma-to-webui
Recreate Figma design frames as production-level Chromium WebUI code following Chrome's Lit-element architecture and styling guidelines. Use when asked to create WebUI code from a Figma frame URL.
figma-to-views-json
Recreate Figma design frames as prototype-ready Chromium Views JSON script following Chrome's native Views architecture, component guidelines, and color/shape token mappings. Use when asked to create C++ Views Prototype JSON script from a Figma frame URL.
figma-to-views
Recreate Figma design frames as production-ready Chromium C++ Views code following Chrome's native Views architecture, component guidelines, and color/shape token mappings. Use when asked to create C++ Views code from a Figma frame URL.