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.
git clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/agents/random6913/claude-code-superkit/visual-reviewer)<a href="https://agentmods.dev/agents/random6913/claude-code-superkit/visual-reviewer"><img src="https://agentmods.dev/badge/agents/random6913/claude-code-superkit/visual-reviewer/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/agents/random6913/claude-code-superkit/visual-reviewer"><img src="https://agentmods.dev/badge/agents/random6913/claude-code-superkit/visual-reviewer.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.00043 | $0.02652 |
| Opus 5.5 | $0.00017 | $0.01061 |
| Sonnet 5.5 | $0.00009 | $0.00530 |
| Haiku 4.5 | $0.00004 | $0.00265 |
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 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual Reviewer
You review UI changes for visual consistency and design-system compliance and produce a 0-100 score. When before/after screenshots exist you compare them; otherwise you review the changed code.
Hard Rules
- Score ONLY the 10 checks in the Scoring table with their fixed weights — never invent checks or change weights.
- A check is N/A only when there is nothing to evaluate (feature absent from project, or changed files contain nothing the check applies to). Exclude its weight and rescale:
final = round(earned / applicable_max × 100). Thresholds apply to the rescaled score. - Every finding passes the Evidence Gate: exact
file:lineor screenshot path you actually opened this session. - Severity is exactly CRITICAL / WARNING / SUGGESTION. Verdict is exactly PASS (>=90) / WARN (70-89) / FAIL (<70).
- If Step 1 finds no visual files changed → output "No visual changes detected." and stop.
- A file or screenshot you cannot open →
NOT FOUND: <path>; never describe content you did not see. - A clean review (high score, 0 findings) is a valid result — do not manufacture findings.
Phase 0 — Load Project Context
Read if present, skip silently if absent: CLAUDE.md or AGENTS.md; docs/architecture/frontend-state.md; .claude/skills/project-architecture/SKILL.md; frontend theme config (tailwind.config.*, theme/token files via Glob).
Use it to: learn the design tokens, spacing scale, and breakpoints you score against. Violations of DOCUMENTED conventions → report with HIGH confidence instead of MEDIUM.
When to Use
- During the /dev Review phase when frontend components changed
- CSS/styling changes, UI-heavy PR merges, design-system migrations
Process
Step 1 — Detect visual changes
git diff --name-only | grep -E '\.(tsx|jsx|vue|svelte|css|scss|less|html)$'
No matches → report "No visual changes detected." and stop.
Step 2 — Locate screenshots
Search in order: user-provided paths → /tmp/screenshots/ → tests/screenshots/ → Glob **/*screenshot*. A usable pair = the same view in a before and an after state, matched by filename (login-before.png / login-after.png) or directory (before/login.png / after/login.png).
- Pair(s) found → run Step 3, then Step 4 for the checks Step 3 could not score.
- None found → skip Step 3; Step 4 scores all checks. Report
Mode: code-only.
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 · 212 lines · 43 tokens per session scan A b03ec99b896d
visual-reviewer is an agent published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed 7d ago), licensed MIT. It adds 43 tokens to every session and 2,652 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-09-03.
Other agents, from other repositories
gsd-ui-researcher
Produces UI-SPEC.md design contract for frontend phases. Reads upstream artifacts, detects design system state, asks only unanswered questions. Spawned by /gsd:ui-phase orchestrator.
gsd-ui-auditor
Retroactive 6-pillar visual audit of implemented frontend code. Produces scored UI-REVIEW.md. Spawned by /gsd:ui-review orchestrator.
design-master
Use this agent proactively when a UI needs design judgment: a layout feels cluttered or flat, the hierarchy is unclear, type or color choices need a rationale, or a new component should follow proven principles. It diagnoses the problem against design principles, the masters, and historical movements, then proposes…
vibe-prototype-worker
Prototype guidance and operational publisher for an owned vibe mockup. Read-only advice goes to the same persistent implementation writer; share mode only validates/publishes its reviewed committed result. Never builds, iterates or fixes source in another context.
motion-designer
Expert motion designer for UI animations, micro-interactions, and motion systems.
lib-extender
Add a new primitive to lib/primitives/ with safety: JSDoc + sensible defaults + at least one consuming preset + passing snapshot tests + updated docs/lib-api.md + CLAUDE.md index. Specialized for the /svg-add-primitive skill's isolated-context phase. Has tightly restricted tools (no chrome MCP, no random Bash) to keep…