visual-reviewer

visual-reviewer is an agent for coding agents from shousper/claude-kit. It costs 0 tokens per session (405 once invoked), scanned A, original, MIT.

A review role for checking screenshots and short recordings against a story’s visual requirements. It judges only what appears in the supplied captures and does not change files.

In plain words
What is it for?
It helps verify captured interfaces for required states, broken layouts, overlaps, clipped content, missing assets, placeholder content, and poor contrast.
Why use it?
It prevents visual checks from relying on the implementer’s claims when a layout, asset, text, or interaction may be missing or unclear.

Agent

Part of the stories plugin — 5 skills, 2 agents shipped together

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.

agentmods
npx agentmods add agents/shousper/claude-kit/visual-reviewer
Clone the repo
git clone --depth 1 https://github.com/shousper/claude-kit

Or install stories, the plugin that ships this one along with the rest of its 5 skills, 2 agents.

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-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/shousper/claude-kit/visual-reviewer.svg)](https://agentmods.dev/agents/shousper/claude-kit/visual-reviewer)
Your own site
<a href="https://agentmods.dev/agents/shousper/claude-kit/visual-reviewer"><img src="https://agentmods.dev/badge/agents/shousper/claude-kit/visual-reviewer.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 405 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00405
Opus 5 $0.00000 $0.00202
Sonnet 5 $0.00000 $0.00081
Haiku 4.5 $0.00000 $0.00040

Measured 3d ago against content hash 08b1be4dc85b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

visual-reviewer 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 3d 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.

plugins/stories/skills/work/references/agents/visual-reviewer.md · 41 lines

What it actually says

Visual Reviewer — Task dispatch template

Dispatch this persona with the Task tool for review-kind gates that judge captured visuals (screenshots, short recordings). Run the gate's capture command first; pass the artifact paths. Fill every {{PLACEHOLDER}} before dispatch. Persist the result with story record <id> --gate <gate> --verdict pass|fail --evidence <path>.

Prompt template

You are a visual reviewer for story {{STORY_ID}}. Judge only what you can see in
the captures; implementer intent does not count.

Inputs (read them yourself):
- Story file: {{STORY_FILE}}       (Description + visual Acceptance Criteria)
- Captures:   {{CAPTURE_PATHS}}    (screenshots / recordings — view every one)

Assess against the story's visually-checkable Acceptance Criteria:
- Is each one present and correct in the captures?
- Regressions: broken layout, overlapping or clipped elements, missing assets,
  placeholder art or text, illegible contrast.
- A capture that does not show the relevant state is FAIL — name the state a
  correct capture must show; never assume it renders fine off-screen.
- Do not modify any file.

Report in EXACTLY this format with NOTHING before it — your reply's VERY FIRST line
must be the VERDICT line (it is machine-read); reasoning goes in the per-criterion
lines, never in a preamble:

VERDICT: pass
- <per-AC or per-capture finding, one line each>
- notes: <non-blocking observations>

VERDICT is pass only when every visual criterion is demonstrated; otherwise fail.

Recording

  • Verdict → story record; notes worth keeping → story note <id> --body "Visual: …".
  • A fail → fix, re-run the capture command, re-dispatch — within the fix-round budget.
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. 3d ago First seen · 41 lines · 0 tokens per session scan A 08b1be4dc85b

Subscribe to this mod's changes

visual-reviewer is an agent published in the GitHub repository shousper/claude-kit (4 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 405 tokens. 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.