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 RaNDoM6913/claude-code-superkit --skill visual-reviewergit 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/skills/random6913/claude-code-superkit/visual-reviewer)<a href="https://agentmods.dev/skills/random6913/claude-code-superkit/visual-reviewer"><img src="https://agentmods.dev/badge/skills/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/skills/random6913/claude-code-superkit/visual-reviewer"><img src="https://agentmods.dev/badge/skills/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.00031 | $0.02185 |
| Opus 5.5 | $0.00012 | $0.00874 |
| Sonnet 5.5 | $0.00006 | $0.00437 |
| Haiku 4.5 | $0.00003 | $0.00218 |
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 8d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual Reviewer
Review the assigned UI change for visual regressions, coherent design and usable presentation. Compare real before/after evidence when available; distinguish source analysis, rendered observations and exercised interaction. A clean scoped review is valid. A high visual score alone does not establish behavioral, accessibility or release acceptance.
Scope, context, and authority
Read applicable AGENTS.md, the accepted design/reference, product requirements and relevant architecture/theme/component conventions. Optional project architecture or frontend-state documents are context only: locate and read them if present, record relevant gaps if absent, and do not require an uninstalled companion skill. Establish revision/diff/base, affected screens, supported environments, mandatory criteria and exclusions. Inspect the actual components, styles, tokens and consumers behind the change.
Identify visual impact through the requested diff and its dependents, including assets, fonts, content, theme/configuration, shared components and routes. File extensions and an empty working-tree diff cannot rule out visual impact in a committed change. Report No visual changes detected. only when the assigned scope supports that conclusion; identify the reviewed scope and N/A rationale. Unknown scope remains unknown.
Review only. Do not edit code/assets/configuration, install packages, update baselines, start applications, navigate a browser, authenticate, capture private screens or execute UI actions solely because a tool is available. Such evidence collection requires actual task authority covering the environment and actions; use existing authorization without asking again. Inspect local check scripts and their hooks, network/write effects before authorized execution. Avoid actions that send messages, submit transactions or alter external state outside that authority. Browser/screenshot tools are optional capabilities, not assumed prerequisites for source review. If required rendered or interaction evidence is inaccessible, report PARTIAL/UNAVAILABLE and block the corresponding mandatory acceptance.
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.
- 8d ago Changed · -9 lines · +10 tokens per session 9290652605b4
- 1mo ago First seen · 95 lines · 21 tokens per session scan A bb409f5fb19b
visual-reviewer is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed 8d ago), licensed MIT. It adds 31 tokens to every session and 2,185 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.
Other skills, from other repositories
impeccable
Create distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics. Use when the user asks to build web components, pages, artifacts, posters, or applications, or when any design skill requires project context. Call with 'craft' for…
ui-architecture
Iris's new UI surface design skill. Takes a brief for a new screen, component, or design system and produces a complete visual architecture spec — component tree, layout grid, interaction states, breakpoints, tokens. No code.
visual-polish
Iris's UI visual polish review skill. Audits an existing UI surface against the four axes — palette, proportion, hierarchy, motion — and returns specific, actionable improvements. No code. Spec output only.
taste-skill
Senior UI/UX Engineer. Architect digital interfaces overriding default LLM biases. Enforces metric-based rules, strict component architecture, CSS hardware acceleration, and balanced design engineering.
gsd-sketch
Sketch UI/design ideas with throwaway HTML mockups, or propose what to sketch next (frontier mode).
gsd-ui-phase
Generate UI design contract (UI-SPEC.md) for frontend phases.