critique-theater

critique-theater is a skill for Claude Code, Codex from nexu-io/open-design. It costs 35 tokens per session (559 once invoked), scanned A, original, Apache-2.0.

A structured review in which five roles—Designer, Critic, Brand, Accessibility, and Copy—score an artifact in rounds and record required fixes. The review is streamed and saved as a replayable transcript.

In plain words
What is it for?
Use it to evaluate generated design artifacts, collect role-specific fixes, and make a documented ship decision.
Why use it?
It brings visual quality, brand fit, accessibility, and wording into one recorded review process.

Skill for Claude CodeCodex

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

Good fit Use it to evaluate generated design artifacts, collect role-specific fixes, and make a documented ship decision.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nexu-io/open-design/critique-theater
About the project

OpenDesign is an open-source, local-first desktop app that lets coding agents create prototypes, dashboards, slide decks, images, video, and design systems as exportable files. It is used by people working with agent runtimes such as Claude Code, Codex, Cursor, and DeepSeek Harness. The catalogue add-ons extend the OpenDesign workflow with skills, instructions, commands, and plugins.

nexu-io/open-design · 95,309 stars · on GitHub · open-design.ai

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 nexu-io/open-design --skill critique-theater
Clone the repo
git clone --depth 1 https://github.com/nexu-io/open-design

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 critique-theater

README.md
[![agentmods](https://agentmods.dev/badge/skills/nexu-io/open-design/critique-theater/github.svg)](https://agentmods.dev/skills/nexu-io/open-design/critique-theater)
Your own site
<a href="https://agentmods.dev/skills/nexu-io/open-design/critique-theater"><img src="https://agentmods.dev/badge/skills/nexu-io/open-design/critique-theater/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 critique-theater

Your own site · 80×15
<a href="https://agentmods.dev/skills/nexu-io/open-design/critique-theater"><img src="https://agentmods.dev/badge/skills/nexu-io/open-design/critique-theater.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 559 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
  • Snyk pass 7 Sept 2026
  • 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.00035 $0.00559
Opus 5 $0.00017 $0.00280
Sonnet 5 $0.00007 $0.00112
Haiku 4.5 $0.00003 $0.00056

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

Security

Grade A, and why

critique-theater 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/_official/atoms/critique-theater/SKILL.md · 56 lines

How it starts

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

Design review

Before you hand an artifact over, review it against five dimensions and fix what falls short. This is a quality bar, not a performance: do the review, apply the fixes, and describe the outcome in ordinary prose.

The five dimensions

Judge the artifact you just produced from five angles. Each one owns its own scope; do not let a strength in one excuse a failure in another.

  • Craft — layout, hierarchy, spacing, alignment, and visual rhythm. Does it read as deliberate work rather than a template with the words swapped out?
  • Critique — does it actually solve the user's stated problem? Look for the weakest claim, the thinnest section, the thing a sceptical reviewer would attack first.
  • Brand — does it follow the active design system's tokens, typography, and voice? A brand violation is a defect even when the result looks pleasant.
  • Accessibility — contrast ratios, touch-target sizes, focus rings, labels on interactive controls and dialogs, keyboard reachability, sensible heading order.
  • Copy — is the text specific, readable, and free of filler? Placeholder phrasing and marketing padding both count as defects.

What to do with the findings

Record each concrete defect and fix it in the same turn. A finding you cannot fix is worth stating plainly, with the reason, so the user can decide.

Keep iterating while defects remain and you still have room to work. Stop when the artifact clears all five dimensions, or when further rounds stop producing real improvements — whichever comes first. Three passes is a sensible ceiling.

OD_MAX_DEVLOOP_ITERATIONS caps the outer plugin pipeline stage; it is not this review's round limit. A pipeline's critique.score signal is a scheduler-facing projection, not something you should write into your answer.

How to report it

Write the outcome the way you would write any other part of your answer: plain prose, in the user's language, saying what you checked, what you fixed, and anything you deliberately left alone.

Read the full file on GitHub · 56 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 Changed · -4 lines · +3 tokens per session dc0d2b0046d2
  2. 8d ago First seen · 60 lines · 32 tokens per session scan A 95b21b641e17

Subscribe to this mod's changes

critique-theater is a skill published in the GitHub repository nexu-io/open-design (95,309 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 559 once invoked, about $0.0002 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-09-03.

Related

Other skills, from other repositories