agentmods.dev

froggo-mission-control: Skill for Claude Code

.claude/skills/design-review/SKILL.md

design-review is a skill for Claude Code from ProfFroggo/froggo-mission-control. It costs 30 tokens per session (2,909 once invoked), scanned A, original, Apache-2.0.

Process for reviewing UI designs or implemented UI against design standards — covering visual hierarchy, accessibility, responsiveness, states, and handoff readiness.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is ProfFroggo/froggo-mission-control's own configuration. It tells Claude Code how to work on froggo-mission-control itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything froggo-mission-control configures →

not rated 2repo 6mo ago A scan 30 tokens original Apache-2.0
View source ↗ ProfFroggo/froggo-mission-control
Reuse

Borrowing it

Nothing to install: this file belongs to ProfFroggo/froggo-mission-control. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ProfFroggo/froggo-mission-control/dev/.claude/skills/design-review/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ProfFroggo/froggo-mission-control

Made for: Claude Code.

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-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/proffroggo/froggo-mission-control/design-review/github.svg)](https://agentmods.dev/skills/proffroggo/froggo-mission-control/design-review)
Your own site
<a href="https://agentmods.dev/skills/proffroggo/froggo-mission-control/design-review"><img src="https://agentmods.dev/badge/skills/proffroggo/froggo-mission-control/design-review/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 design-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/proffroggo/froggo-mission-control/design-review"><img src="https://agentmods.dev/badge/skills/proffroggo/froggo-mission-control/design-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,909 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.00030 $0.02909
Opus 5.5 $0.00012 $0.01164
Sonnet 5.5 $0.00006 $0.00582
Haiku 4.5 $0.00003 $0.00291

Measured today against content hash fa4f67900398, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

design-review 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 today.

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.

.claude/skills/design-review/SKILL.md · 340 lines

How it starts

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

Design Review

Purpose

Review UI designs and implemented interfaces systematically against a consistent set of quality dimensions. Every design review produces clear, actionable feedback with severity levels — not subjective opinions. The goal is to ship interfaces that are accessible, consistent, and complete.

Trigger Conditions

Load this skill when:

  • Reviewing Figma designs before engineering implementation begins
  • Reviewing implemented UI (in browser or staging) against design specs
  • Auditing existing UI for accessibility or design standard compliance
  • Completing a design-to-dev handoff
  • Signing off on a feature before it ships to production

Procedure

Step 1 — Understand Scope Before Reviewing

Before starting a review:

What is being reviewed: [Figma file / staging URL / production URL / screenshots]
Review type: [Design review (pre-build) / Implementation review (post-build) / Accessibility audit]
Feature or scope: [specific screen, flow, or component]
Platform: [Desktop web / Mobile web / Both]
Design standard reference: [which design system or guidelines apply]

Read any existing PRD or design brief before reviewing. Do not review in a vacuum — understand what the design is supposed to do before evaluating how well it does it.

Step 2 — Review Dimensions

Evaluate every design across all of these dimensions. Do not skip dimensions because a design "looks good."

Dimension 1: Visual Hierarchy

Is it immediately clear what the most important element on the page is? Can a user understand what to look at first, second, third?

Check:

  • Is there a clear primary action (one dominant CTA per screen)?
  • Does text size and weight create a logical reading order?
  • Is whitespace used to group related elements and separate unrelated ones?
  • Does the eye flow naturally through the design, or does it feel chaotic?

Questions to ask:

  • "What is the first thing a user sees when they land on this screen?"
  • "Is there visual competition between elements that should not compete?"

Read the full file on GitHub · 340 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. today First seen · 340 lines · 30 tokens per session scan A fa4f67900398

Subscribe to this mod's changes

design-review is a skill published in the GitHub repository ProfFroggo/froggo-mission-control (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 2,909 once invoked, about $0.0001 per session on Opus 5.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-11-07.

Code reviewDesign and UXFrontend
Related

design-review compared with skills from other repositories

design-review next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
design-reviewProfFroggo/froggo-mission-controlSkill26mo agoApache-2.0A30Claude Code
critique-theaternexu-io/open-designSkill106kyesterdayApache-2.0A35Claude Code, Codex
design-reviewPrismer-AI/PrismerCloudSkill1.4k15d agoMITA84Claude Code
nw-fp-usable-designnWave-ai/nWaveSkill631yesterdayMITA20Claude Code
cinematic-shotdzhng/skillsSkill1.4k2d agoMITA127Claude Code, Codex
compare-screenshotsdzhng/skillsSkill1.4k2d agoMITA51Claude Code, Codex
design-with-imagesdzhng/skillsSkill1.4k2d agoMITA55Claude Code, Codex