mobile-design-evaluator

mobile-design-evaluator is an agent for coding agents from ShipWithAI/shipwithai-plugins. It costs 96 tokens per session (1,867 once invoked), scanned A, original, MIT.

A reviewer that grades already-rendered mobile interface screenshots against a design checklist and returns a pass or fail verdict with specific fixes.

In plain words
What is it for?
Use it after a screenshot inspection harness has rendered PNG files. It checks the screenshots, reports element-level issues, and fails clearly when the harness has not been run.
Why use it?
It provides an independent visual check after another developer changes a Compose screen, helping catch layout and usability problems without changing the source code.

Agent

Part of the shipwithai-mobile-ui-harness plugin — 2 skills, 3 commands, 1 agent 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/shipwithai/shipwithai-plugins/mobile-design-evaluator
Clone the repo
git clone --depth 1 https://github.com/ShipWithAI/shipwithai-plugins

Or install shipwithai-mobile-ui-harness, the plugin that ships this one along with the rest of its 2 skills, 3 commands, 1 agent.

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 mobile-design-evaluator

README.md
[![agentmods](https://agentmods.dev/badge/agents/shipwithai/shipwithai-plugins/mobile-design-evaluator.svg)](https://agentmods.dev/agents/shipwithai/shipwithai-plugins/mobile-design-evaluator)
Your own site
<a href="https://agentmods.dev/agents/shipwithai/shipwithai-plugins/mobile-design-evaluator"><img src="https://agentmods.dev/badge/agents/shipwithai/shipwithai-plugins/mobile-design-evaluator.svg" alt="Measured on agentmods" height="20"></a>
Per session 96 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,867 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.00096 $0.01867
Opus 5 $0.00048 $0.00933
Sonnet 5 $0.00019 $0.00373
Haiku 4.5 $0.00010 $0.00187

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

Security

Grade A, and why

mobile-design-evaluator 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 5d 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/mobile-ui-harness/agents/mobile-design-evaluator.md · 107 lines

How it starts

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

You are the mobile-design evaluator for this Compose Multiplatform project. You grade already-rendered UI screenshots. You are the critic half of an executor-evaluator loop: a separate lane edited the @Composable and rendered it; your job is to judge the result.

The one rule

You evaluate, you do not generate. Never edit a @Composable, a theme file, or any source. Your only write is the verdict file. If you are tempted to "just fix it," stop — the fix belongs to the executor; you describe it precisely so they can. Judging code you also wrote is self-review, which this loop exists to prevent.

Inputs

Your dispatch prompt gives you one or both of:

  • a directory of rendered PNGs (default: feature/*/build/outputs/roborazzi/), and/or an explicit list of PNG paths;
  • optionally, what changed (the screen, the edit) — use it to focus, but still grade every config.

If you were given only a directory, Glob it for _inspect_*.png. If you find no PNGs, do not guess — return a verdict of fail stating the harness has not been run, and give the exact command (./gradlew :<module>:testAndroidHostTest --tests "...<Screen>Inspection" -Proborazzi.test.record=true).

Protocol

  1. Load the rubric. Read .claude/skills/mobile-design/SKILL.md — it is the source of truth for Tier-1 (structural blockers), Tier-2 (weighted taste), the anti-patterns, and the verdict format. Do not grade from memory; the rubric evolves. Follow its ordering: structural first.

  2. Enumerate the matrix. Filenames are _inspect_<screen>_<config>.png. Decode each into its screen id and its config so you can attribute every defect precisely.

    • screen id: the FIRST token after _inspect_ (songs, field, picker) — the component under test. Use it verbatim as the screen field so your rows cluster with the deterministic Tier-1 findings. One inspection dir can mix components (e.g. field + picker), so read this per-PNG — never stamp one screen name across the whole dir.
    • width: 360 = compact (~360dp), 411 = reference (~411dp), compact/default synonyms;
    • font scale: font1_5 = 1.5, font2_0 = 2.0, otherwise 1.0;
    • theme: a _dark suffix = dark mode, else light;
    • content: long, empty, error name the state, otherwise the default/happy path. If a name is ambiguous, infer the config from the rendered image (text size, width) instead.

Read the full file on GitHub · 107 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. 5d ago First seen · 107 lines · 96 tokens per session scan A bb095ff97601

Subscribe to this mod's changes

mobile-design-evaluator is an agent published in the GitHub repository ShipWithAI/shipwithai-plugins (10 stars, last pushed 23d ago), licensed MIT. It adds 96 tokens to every session and 1,867 once invoked, about $0.0005 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-31.

Related

Other agents, from other repositories

developer

Use when execute-round's Phase 3 (dev body) needs to implement BA design exactly. Writes source + tests per file decomposition, runs pre-audit quality gates, registers forward-debts, and reports diff summary.

Arch1eSUN/Arcgentic · 47 tokens

agents-expert

Expert on creating and configuring custom Claude Code agents (subagents). Use PROACTIVELY when the user mentions creating an agent, custom agent, or subagent; when designing specialized agents for project tasks; when troubleshooting agent invocation, tools, or model config; or during /agents-generate. Knows the…

claude-world/director-mode-lite · 138 tokens

autoevolve-optimizer

Autonomous optimization loop for config artifacts (detection-index, context-router) - mutate, score deterministically, keep only improvements. Two code-enforced safety gates wrap the loop.

primeline-ai/evolving-lite · 36 tokens

health-monitor

Deep health analysis of Evolving Lite - sentinel history, hook performance, recommendations.

primeline-ai/evolving-lite · 15 tokens

codex-rescue

Hand an OPEN-ENDED or stuck problem to Codex for independent investigation. Use ONLY when the user says "stuck", "second opinion", "rescue", "dig deeper", "I'm not sure why X", OR hands off a substantial unbounded task with no written plan. Do NOT use when a plan or plan-step file is in context (use codex-execute) or…

greenpolo/cc-multi-cli-plugin · 99 tokens

cursor-explore

Delegate quick read-only CODEBASE exploration to Cursor. Use to answer questions about the current repository ("where is X handled?", "how does Y flow?", "summarize the adapter layer") without spending Claude's tokens reading files. Cursor runs read-only (ask mode) using semantic search, grep, and its Explore…

greenpolo/cc-multi-cli-plugin · 90 tokens