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 agentmods add skills/dsifry/metaswarm/visual-reviewnpx skills add dsifry/metaswarm --skill visual-reviewgit clone --depth 1 https://github.com/dsifry/metaswarmWrote 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/dsifry/metaswarm/visual-review)<a href="https://agentmods.dev/skills/dsifry/metaswarm/visual-review"><img src="https://agentmods.dev/badge/skills/dsifry/metaswarm/visual-review.svg" alt="Measured on agentmods" 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.00018 | $0.01902 |
| Opus 5 | $0.00009 | $0.00951 |
| Sonnet 5 | $0.00004 | $0.00380 |
| Haiku 4.5 | $0.00002 | $0.00190 |
Grade A, and why
visual-review 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 6d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual Review
Purpose
Agents cannot see rendered web pages, presentations, or UI. This skill bridges that gap by using Playwright to capture screenshots of web pages (local files, localhost servers, or deployed URLs) so agents can visually inspect their work, identify layout issues, and iterate.
This is especially useful for:
- Reveal.js presentations — capture each slide individually
- Web UIs — verify layout, styling, and responsiveness
- Landing pages — check visual design matches intent
- Email templates — verify rendering
Prerequisites
This skill requires Playwright to be available. Before first use, check and install if needed:
# Check if Playwright is available
npx playwright --version 2>/dev/null
# If not available, install it (one-time setup)
npx playwright install chromium
Important: Only the chromium browser is needed. Do not install all browsers — it wastes disk space and time.
If npx playwright fails entirely, the user may need to install it:
npm install -g playwright
npx playwright install chromium
Workflow
Phase 1: Setup
- Verify Playwright is available — run
npx playwright --version - If not installed — run
npx playwright install chromiumand inform the user - Create output directory —
mkdir -p /tmp/visual-review - Determine the target — local file path, localhost URL, or deployed URL
Phase 2: Capture Screenshots
For a single page:
npx playwright screenshot \
--browser chromium \
--viewport-size "1456,816" \
--wait-for-timeout 3000 \
"<URL_OR_FILE_PATH>" \
/tmp/visual-review/page.png
Parameters:
--viewport-size "1456,816"— 16:9 aspect ratio, good for presentations--wait-for-timeout 3000— wait 3 seconds for fonts, images, and animations to settle- Use
file:///absolute/path/to/file.htmlfor local files - Use full URLs for deployed sites
For Reveal.js presentations (multiple slides):
Capture each slide by appending the slide hash to the URL:
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.
- 6d ago First seen · 225 lines · 18 tokens per session scan A 826be0844d54
visual-review is a skill published in the GitHub repository dsifry/metaswarm (413 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 1,902 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-30.
Other skills, from other repositories
figma-to-webui
Recreate Figma design frames as production-ready Chromium WebUI code following Chrome's Lit-element architecture and styling guidelines. Use when asked to create WebUI code from a Figma frame URL.
generate-component-spec
Maps a Figma component from the Chrome Design System (CDS) to equivalent C++ Views, WebUI, and Clank (Android) components in the Chromium codebase. Generates a comprehensive side-by-side comparative Markdown specification detailing layout variants, interactive states, design tokens, architectural and implementation…
generate-token-map
Maps all Figma design tokens from figma-variables.md to their equivalent C++ (Views) identifiers, CSS (WebUI) variables, and Clank (Android) resource attributes/macros/methods in Chromium, and saves the formatted mapping table to the assets directory of the Chrome Design System project. Use this skill when asked to…
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.
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.