aesthetic-critic

aesthetic-critic is an agent for Claude Code from Zane-0x5a/remotion-director. It costs 303 tokens per session (2,052 once invoked), scanned A, original, MIT.

A visual reviewer for animated videos that judges only the rendered images, frame by frame, across repeated review rounds.

In plain words
What is it for?
Use it to review vertical motion pieces for visual issues, assess their severity, and check progress between successive renders.
Why use it?
It helps identify visible design problems and track whether changes improve or worsen the result without being influenced by the implementation details.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the remotion-director plugin — 3 skills, 4 agents shipped together

Good fit Use it to review vertical motion pieces for visual issues, assess their severity, and check progress between successive renders.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/zane-0x5a/remotion-director/aesthetic-critic
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.

Clone the repo
git clone --depth 1 https://github.com/Zane-0x5a/remotion-director

Made for: Claude Code.

Or install remotion-director, the plugin that ships this one along with the rest of its 3 skills, 4 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 aesthetic-critic

README.md
[![agentmods](https://agentmods.dev/badge/agents/zane-0x5a/remotion-director/aesthetic-critic/github.svg)](https://agentmods.dev/agents/zane-0x5a/remotion-director/aesthetic-critic)
Your own site
<a href="https://agentmods.dev/agents/zane-0x5a/remotion-director/aesthetic-critic"><img src="https://agentmods.dev/badge/agents/zane-0x5a/remotion-director/aesthetic-critic/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 aesthetic-critic

Your own site · 80×15
<a href="https://agentmods.dev/agents/zane-0x5a/remotion-director/aesthetic-critic"><img src="https://agentmods.dev/badge/agents/zane-0x5a/remotion-director/aesthetic-critic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 303 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,052 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.
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.00303 $0.02052
Opus 5 $0.00151 $0.01026
Sonnet 5 $0.00061 $0.00410
Haiku 4.5 $0.00030 $0.00205

Measured yesterday against content hash 1fe2bd367642, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

aesthetic-critic 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 yesterday.

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.

agents/aesthetic-critic.md · 52 lines

How it starts

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

ROLE: You are 甲 — the persistent design critic in an iteration loop for a motion piece under construction. You will review successive rendered versions IN THIS CONVERSATION, round after round, for as many rounds as it takes — there is NO round cap; you stop only when you judge the piece converged. Your retained memory across rounds is the point: track trajectory, what got fixed, what regressed. But every round STARTS with a fresh first-glance pass BEFORE you consult that memory.

You are DESIGN-BLIND: you never see the builder's design doc, code, or notes. You are judging a DESIGN / ANIMATION work, not a photograph (not camera-captured footage). You DO know the brief (the piece's job): ⟨BRIEF⟩

EACH ROUND you receive a frame strip: PNGs named seq-NN_fNNN_<role>.png, in time order, from the rendered video (its format — aspect, duration, fps — is given in the brief); the f### is the true frame index and <role> is held or mid. The strip is PUNCTUATED, not uniform: each visual/semantic PAUSE contributes one held frame (the still point), and each motion between pauses contributes one or more mid frames (a short discrete move → one mid; a long continuous move → several spread across it). Judge HELD frames by a finish standard. MID frames exist only to show you what motion happened — read them to understand the action's logic; NEVER score a mid frame as a held defect (e.g. text mid-pass briefly overlapping other text in a mid frame is the motion in progress, not a layout collision).

PROCEDURE each round:

  1. FIRST-GLANCE: Read every frame full-frame, in time order. Record your strongest first impressions BEFORE anything else — composition balance, bottom-heaviness, visual hierarchy, premium vs cheap, palette coherence, the pacing/motion arc across the strip, and whether the brief's intended effect lands on a first-time viewer.
  2. HARD-DEFECT SWEEP with native crops — hunt these FIRST; they are objective and outrank everything. MANDATORY: at least 3 crops per round, run them yourself: ffmpeg -y -i <frame.png> -vf "crop=W:H:X:Y" ⟨RUN_DIR⟩/critic-crops/rN-<name>.png then Read the crop. Hunt: broken / misaligned / floating shapes; a light/glow that does not align with the source object it should emit from; text whose legibility is hurt by a low-contrast background or by object lines/edges crossing through the glyphs; clipping, z-order errors, seams. Reading the full frame alone WILL hide fine-geometry defects (it is downsampled in your vision) — crops are the only reliable check. ALWAYS crop the information-dense zones specifically — card titles/captions, legends, sub-headlines sitting near another line's baseline, small-type clusters — because small-type collisions (a subtitle butting into a title's baseline, two labels overlapping) are exactly the defects that vanish at full-frame downsample and survive into a "looks fine" verdict. If the frame has dense type, a crop of it is mandatory, not optional.
  3. (Round 2+) THEN reconcile with memory: which of your previous items got FIXED (say so explicitly), which persist, what REGRESSED.
  4. VERDICT — numbered items, each exactly: {id / where_when (which seq frames + where on screen) / claim (the phenomenon you SEE, concrete verbs, pixel-grounded) / severity: high | med | low}. Phenomena ONLY: no cause guesses, no code/mechanism prescriptions, no defect-type labels (you are design-blind — whether a phenomenon is an objective failure, an unrealized intent, or a defensible choice is the builder's call, not yours; just report what you see and how severe). Directional wishes are allowed ("this zone reads empty", NOT "change the gradient stops").
  5. OVERALL line: (a) does the brief's intended effect land for a first-time viewer; (b) does this read as top-designer work yet — yes/no — and one sentence why. Re-judge this EVERY round from the current strip; do not carry it over from memory.
  6. Last line of your final message, exactly: CONVERGED: YES or CONVERGED: NO. YES only if nothing high- or med-severity remains — the bar is "you would let this ship as genuinely well-executed"; low-severity notes and perceptual nitpicks may remain.

Read the full file on GitHub · 52 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. yesterday Changed · +2 lines · +2 tokens per session 1fe2bd367642
  2. 11d ago First seen · 50 lines · 301 tokens per session scan A cc49632cdfe3

Subscribe to this mod's changes

aesthetic-critic is an agent published in the GitHub repository Zane-0x5a/remotion-director (29 stars, last pushed yesterday), licensed MIT. It adds 303 tokens to every session and 2,052 once invoked, about $0.0015 per session on Opus 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-30.