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 atre/looksy --skill visual-qagit clone --depth 1 https://github.com/atre/looksyWrote 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/atre/looksy/visual-qa)<a href="https://agentmods.dev/skills/atre/looksy/visual-qa"><img src="https://agentmods.dev/badge/skills/atre/looksy/visual-qa/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/atre/looksy/visual-qa"><img src="https://agentmods.dev/badge/skills/atre/looksy/visual-qa.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.00115 | $0.01183 |
| Opus 5.5 | $0.00046 | $0.00473 |
| Sonnet 5.5 | $0.00023 | $0.00237 |
| Haiku 4.5 | $0.00012 | $0.00118 |
Grade A, and why
visual-qa 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual QA Workflow (looksy)
Screenshots show THAT something looks wrong; the sidecar (--meta/--compact) shows WHY (font-size, padding, colors, contrast). Full flag reference: ~/git/looksy/.claude/rules/flag-behavior.md. Off PATH → node ~/git/looksy/bin/looksy.js.
Core loop
looksy --serve # once; detached, idempotent (--serve-stop to kill)
looksy <url> --design --name baseline # --full --meta --compact --fonts --css-vars --contrast --suggest (~1k tokens)
[make changes]
looksy <url> --design --name v1
looksy <url> --diff-inline /tmp/looksy/preview-baseline.png # pixel side-by-side → preview-diff.png
looksy <url> --delta # ~80 tokens: metadata diff vs previous capture
looksy <url> --check "contrast:aa, no-hscroll, text:Expected" # ~50 tokens, exit 1 on fail
--name/-o/--suffix force the PNG even in text-only modes (--report, --check). Stale DNS after a cutover: --host-resolver domain:ip.
Cost / mode picker
| Mode | Tokens | Use |
|---|---|---|
--check "…" |
~50 | assertion pass/fail (CI, hooks) |
--report / --delta |
~100 / ~80 | text-only summary / changed props only |
--design |
~1,000 | design review |
--design-audit |
~1,200 | pre-launch gate: + --seo --schema --font-sources --responsive-check --check "no generator, self-hosted-fonts, contrast:aa" |
--speed |
~2,500 | perf: perf/network/coverage/bundles/images/compression/third-party/cache/critical-path/hints/server-timing/image-optimizer |
Fleet / batch
looksy fleet https://a.com https://b.com --design-audit -q # N URLs, shared browser, batch-report.md, exit 1 on AA fail
looksy fleet --design-audit # no URLs → ./fleet.yaml (domains × pages; --fleet <path> to override)
looksy fleet --brief # red-only ≤10 lines: `✗ <url> — HTTP 404, hscroll +21px, 2 AA fail` | `✓ N URLs clean`
looksy fleet https://a.com https://b.com -o out/ # -o dir/ → one preview-<slug>.png + sidecar per URL (else last URL wins)
looksy <url> --pages "/,/pricing,/about" --design --consistency --batch-report # same-domain, cross-page consistency
looksy <url> --links --links-allow "linkedin.com,x.com" # dead links; allow-list hosts → `unverifiable`, not dead
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 · 59 lines · 115 tokens per session scan A 932ec5d7f71f
visual-qa is a skill published in the GitHub repository atre/looksy (0 stars, last pushed 1mo ago), licensed MIT. It adds 115 tokens to every session and 1,183 once invoked, about $0.0005 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.