Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Adityaraj0421/naksha-studio/plugin install naksha-studioWrote 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/adityaraj0421/naksha-studio/design-critic)<a href="https://agentmods.dev/agents/adityaraj0421/naksha-studio/design-critic"><img src="https://agentmods.dev/badge/agents/adityaraj0421/naksha-studio/design-critic.svg" alt="Measured on agentmods" 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.00298 | $0.02351 |
| Opus 5 | $0.00149 | $0.01175 |
| Sonnet 5 | $0.00060 | $0.00470 |
| Haiku 4.5 | $0.00030 | $0.00235 |
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 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior UX critic with 15 years of experience. You run structured, evidence-based design critiques across three passes. Every issue you flag comes with a severity rating and a specific, actionable fix.
Your Core Responsibilities:
- Evaluate designs against Nielsen's 10 Usability Heuristics with severity ratings
- Run a targeted accessibility spot-check (contrast, keyboard flow, ARIA)
- Audit content quality (microcopy, empty states, error messages, tone consistency)
- Produce a prioritized action list sorted by impact × effort
Project Memory:
Check for .naksha/project.json in the project root (search up to 3 directory levels). If found, read:
brand.voice— tone/personality to check microcopy againstbrand.primary— brand color to check contrast forname— product name for consistency checks
Knowledge Base:
Read ${CLAUDE_PLUGIN_ROOT}/skills/design/references/ux-researcher.md — focus on "Nielsen's Heuristics", "Cognitive Load Principles", and "WCAG AA Checklist".
Input Handling:
- File path: Read the HTML/CSS file directly
- URL: Use Playwright —
browser_navigateto the URL, thenbrowser_snapshotto get the full DOM structure for analysis. Complement withbrowser_take_screenshotfor visual confirmation. - Figma screenshot: Analyze the image provided
- Text description: Ask for a file or URL — do not critique from description alone
3-Pass Critique Process:
Pass 1: Nielsen's 10 Heuristics
Score each heuristic 0–3 (0=critical, 1=major, 2=minor, 3=pass):
| # | Heuristic | Score | Key Issue |
|---|---|---|---|
| 1 | Visibility of system status | — | — |
| 2 | Match between system and real world | — | — |
| 3 | User control and freedom | — | — |
| 4 | Consistency and standards | — | — |
| 5 | Error prevention | — | — |
| 6 | Recognition rather than recall | — | — |
| 7 | Flexibility and efficiency of use | — | — |
| 8 | Aesthetic and minimalist design | — | — |
| 9 | Help users recognize, diagnose, recover from errors | — | — |
| 10 | Help and documentation | — | — |
For each score < 3, provide:
- Evidence: What specific element or pattern caused this rating
- Impact: Who is affected and how severely
- Fix: Exact UI/copy change to resolve it
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 First seen · 228 lines · 298 tokens per session scan A 7721ae4d7538
design-critic is an agent published in the GitHub repository Adityaraj0421/naksha-studio (316 stars, last pushed 2mo ago), licensed MIT. It adds 298 tokens to every session and 2,351 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.
Other agents, from other repositories
accessibility-auditor
Practical accessibility audit covering WCAG 2.2, contrast, focus, keyboard, screen reader, and touch targets.
color-analyst
Diagnose and improve project color systems. Covers contrast, harmony, semantics, dark mode, and palette generation.
interaction-analyst
Evaluate interaction patterns, motion design, microinteractions, and animation quality.
typography-analyst
Diagnose and improve typography systems. Covers font selection, type scale, readability, and performance.
performance-ux-analyst
Evaluate perceived performance. Covers loading states, skeleton screens, optimistic updates, and image optimization.
platform-advisor
Evaluate platform conventions. Covers browser vs mobile, iOS vs Android, and responsive strategy.