visual-review-pipeline

visual-review-pipeline is a skill for Claude Code, Codex from ils15/pantheon-legacy. It costs 32 tokens per session (1,825 once invoked), scanned A, original, MIT.

A workflow for checking a website or interface with screenshots. It uses Playwright, a browser testing tool, to inspect layout, contrast, responsive behavior, and accessibility, then repeats fixes when needed.

In plain words
What is it for?
Use it to review implemented pages or components at different screen sizes and identify visual regressions.
Why use it?
It helps catch visual problems that ordinary code checks may miss.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to review implemented pages or components at different screen sizes and identify visual regressions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ils15/pantheon-legacy/visual-review-pipeline
Install

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.

Any agent
npx skills add ils15/pantheon-legacy --skill visual-review-pipeline
Clone the repo
git clone --depth 1 https://github.com/ils15/pantheon-legacy

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for visual-review-pipeline

README.md
[![agentmods](https://agentmods.dev/badge/skills/ils15/pantheon-legacy/visual-review-pipeline/github.svg)](https://agentmods.dev/skills/ils15/pantheon-legacy/visual-review-pipeline)
Your own site
<a href="https://agentmods.dev/skills/ils15/pantheon-legacy/visual-review-pipeline"><img src="https://agentmods.dev/badge/skills/ils15/pantheon-legacy/visual-review-pipeline/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.

agentmods 80×15 button for visual-review-pipeline

Your own site · 80×15
<a href="https://agentmods.dev/skills/ils15/pantheon-legacy/visual-review-pipeline"><img src="https://agentmods.dev/badge/skills/ils15/pantheon-legacy/visual-review-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,825 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.01825
Opus 5.5 $0.00013 $0.00730
Sonnet 5.5 $0.00006 $0.00365
Haiku 4.5 $0.00003 $0.00183

Measured 1mo ago against content hash f6e65ff75a93, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

visual-review-pipeline 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.

skills/visual-review-pipeline/SKILL.md · 201 lines

How it starts

The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Visual Review Pipeline

Automated visual review: Aphrodite captures screenshots via Playwright MCP → Self-analyzes for visual issues → Addresses findings in a loop.

Overview

This pipeline establishes a formal workflow for detecting and resolving visual regressions and design issues. It enforces structured JSON output, iteration limits, and escalation criteria to prevent infinite fix loops.

Pipeline Flow

Aphrodite implements UI
    ↓
Playwright screenshot (browser/screenshotPage)
    ↓
Aphrodite self-analyzes (layout, contrast, responsive, accessibility)
    ↓
├─ verdict: pass → proceed to Themis review
├─ verdict: fail + iteration < 3 → fix → re-capture
└─ verdict: fail + iteration = 3 → Zeus escalation

Workflow Steps

Step 1: Capture

Aphrodite uses Playwright MCP to capture screenshots.

  • Navigate to target URL or render component
  • Capture full-page screenshot via browser/screenshotPage
  • Capture viewport-specific screenshots for responsive checks
  • Name files descriptively: screenshot-iteration-N-component.png

Step 2: Analyze

Aphrodite self-analyzes screenshots visually.

  • Examine screenshot(s) for visual issues
  • Identify problems in layout, contrast, responsive behavior, and accessibility
  • Return findings in the structured JSON schema (below)
  • Include iteration number in findings
  • Mark issues with pass_if_fixed IDs

Step 3: Fix

Aphrodite addresses each finding from self-analysis.

  • Triage findings by severity (critical → high → medium → low)
  • Fix each issue in component code
  • Commit changes with descriptive message
  • Re-capture screenshot for next iteration

Step 4: Loop

Repeat Steps 1-3 for up to 3 iterations.

  • Each iteration must fix at least one pass_if_fixed issue
  • Track iteration count in findings object
  • If no progress detected (zero fixes applied), escalate immediately
  • Compare before/after screenshots to verify fixes

Step 5: Escalate

Zeus intervenes if issues persist after 3 iterations.

  • Trigger: 3 iterations exhausted or zero-progress detected
  • Action: Zeus coordinates manual review or architectural decision

Read the full file on GitHub · 201 lines

Changes

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.

  1. 1mo ago First seen · 201 lines · 32 tokens per session scan A f6e65ff75a93

Subscribe to this mod's changes

visual-review-pipeline is a skill published in the GitHub repository ils15/pantheon-legacy (12 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 1,825 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-09-03.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

interactive-login

Log a CLI in with a browser/device-code flow (aws sso, gh, glab, gcloud, …) and save the result to the keychain so later commands can request it through execute.credentials.

yc-software/qm · 46 tokens

pinchtab-mcp

Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.

pinchtab/pinchtab · 52 tokens

azure-messaging-webpubsub-java

Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications.

microsoft/skills · 43 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

open-design-browser

Inspect and exercise local HTML design artifacts and library prototype previews with the existing agent-browser CLI, including screenshots, interaction checks, and rendered DOM snapshots. Use when rendered evidence helps author or review a design; excludes browser installation, remote services, and unrelated browser…

compozy/compozy · 56 tokens