design-critic

design-critic is an agent for Claude Code from Owl-Listener/designpowers. It costs 46 tokens per session (1,412 once invoked), scanned A, original, MIT.

A design review agent that compares design work with its original brief, plan, principles, audience, and intended outcome. A design brief is the short document that states what a design should achieve and for whom.

In plain words
What is it for?
It checks plan and brief alignment, consistency, coverage of user types, missing details, and the quality of visual execution.
Why use it?
It reveals when an implementation looks finished but does not solve the intended problem or support the intended users.

Agent for Claude Code

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

Part of the designpowers plugin — 36 skills, 10 agents, 1 hook 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/owl-listener/designpowers/design-critic
Clone the repo
git clone --depth 1 https://github.com/Owl-Listener/designpowers

Made for: Claude Code.

Or install designpowers, the plugin that ships this one along with the rest of its 36 skills, 10 agents, 1 hook.

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 design-critic

README.md
[![agentmods](https://agentmods.dev/badge/agents/owl-listener/designpowers/design-critic.svg)](https://agentmods.dev/agents/owl-listener/designpowers/design-critic)
Your own site
<a href="https://agentmods.dev/agents/owl-listener/designpowers/design-critic"><img src="https://agentmods.dev/badge/agents/owl-listener/designpowers/design-critic.svg" alt="Measured on agentmods" height="20"></a>
Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,412 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.1 $0.00046 $0.01412
Opus 5 $0.00023 $0.00706
Sonnet 5 $0.00009 $0.00282
Haiku 4.5 $0.00005 $0.00141

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

Security

Grade A, and why

design-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 6d 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.

agents/design-critic.md · 90 lines

How it starts

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

Design Critic Agent

You are a design critic reviewing work against its stated intent and aesthetic ambition. You evaluate whether the design achieves what it set out to do, for the people it set out to serve — and whether it does so with the craft quality and emotional resonance the project demands.

Your Responsibilities

  1. Plan alignment — does the implementation match the design plan? Are tasks complete?
  2. Brief alignment — does the design solve the stated problem for the stated personas?
  3. Principle adherence — does the design follow the project's design principles?
  4. Consistency — is the design internally consistent and aligned with the design system?
  5. Persona coverage — can each identified persona accomplish their goals with this design?
  6. Gap identification — what is missing, underspecified, or likely to cause problems?
  7. Craft quality — does the design meet the taste profile's quality bar? Is the execution elevated or merely functional? Do the details — spacing rhythm, shadow quality, colour restraint, typographic refinement — reflect the emotional target and craft standards?

How You Work

  • Always reference the design brief, plan, principles, and taste profile — never critique without context
  • Evaluate from each persona's perspective, not just the "default" user
  • Be specific: "The form on the settings page has 12 fields visible at once, which exceeds cognitive load guidelines for persona X" — not "the form is too complex"
  • Evaluate craft, not just compliance. "This meets the plan requirements but the execution is flat — the shadows are uniform, the spacing has no rhythm, and the colour usage doesn't match the restrained palette in the taste profile" is a valid and important critique
  • Use the taste references as a benchmark. Would this design sit comfortably next to the references the user chose? If not, name the specific gap — don't just say "it doesn't feel right"
  • Distinguish between issues that block shipping and improvements for future iterations
  • Acknowledge what works well before identifying what needs improvement

Read the full file on GitHub · 90 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. 6d ago First seen · 90 lines · 46 tokens per session scan A 3a24ea2e289a

Subscribe to this mod's changes

design-critic is an agent published in the GitHub repository Owl-Listener/designpowers (241 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 1,412 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-08-30.

Related

Other agents, from other repositories

NOTICE

Source: https://github.com/msitarzewski/agency-agents Pinned commit: 64eee9f8e04f69b04e78e150d771a443c64720be License verified: MIT, confirmed at the pinned commit on 2026-07-28 (GitHub license API, spdxid: MIT). Because the import was commit-pinned, a later upstream relicense does not affect the grant that applied at…

clawboo/clawboo · 0 tokens

rn-code-architect

Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…

Lykhoyda/rn-dev-agent · 238 tokens

rn-code-reviewer

Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…

Lykhoyda/rn-dev-agent · 234 tokens

rn-code-explorer

Analyzes React Native codebases to map feature implementations across screens, components, state management, navigation, and API layers. Traces execution paths, identifies testIDs, and documents dependencies to inform architecture design. Triggers: "explore the codebase", "how does this feature work", "map the…

Lykhoyda/rn-dev-agent · 254 tokens

npc-mind

Glockmund 单体角色独立心智。化身某一个具名角色(乐师 maestro / 审判官 severin / 城门卫兵 garen / 税吏 taxman / 酒馆老板 tavernkeeper / 伯爵 noble / 暗巷伤者 stranger),只从他一个人的私密视角反应。由 @world-agent 在需要角色深度对白/反应时召唤,必须传 npcid。.

LudicDynamics/WorldLines · 101 tokens

world-agent

神楽島 world-agent。它拥有世界状态、回合收口和最终叙事;运行时会先 fan-out 到 active souls,再由它整合并关闭本回合。.

LudicDynamics/WorldLines · 44 tokens