What is design-status?

A status-checking skill for a running design review, where several agents inspect and improve a user interface in stages.

Use it to see the reviewed file, current phase, completed agents, applied fixes and remaining work during or after a design review.

It removes the need to open progress files and work out which review stages or fixes are finished. It also reports when no active review can be found.

How andrejkanuch/design-lenses configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to andrejkanuch/design-lenses. 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/andrejkanuch/design-lenses/main/.claude/skills/design-status/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/andrejkanuch/design-lenses

Made for: Claude Code.

Or install design-lenses, the plugin that ships this one along with the rest of its 3 skills.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/andrejkanuch/design-lenses/design-status/github.svg)](https://agentmods.dev/skills/andrejkanuch/design-lenses/design-status)

Your own site

<a href="https://agentmods.dev/skills/andrejkanuch/design-lenses/design-status"><img src="https://agentmods.dev/badge/skills/andrejkanuch/design-lenses/design-status/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/andrejkanuch/design-lenses/design-status"><img src="https://agentmods.dev/badge/skills/andrejkanuch/design-lenses/design-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,159 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.

Model	Per session	Once invoked
Fable 5.1	$0.00040	$0.01159
Opus 5	$0.00020	$0.00580
Sonnet 5	$0.00008	$0.00232
Haiku 4.5	$0.00004	$0.00116

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

Security

Grade A, and why

design-status 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 11d 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.

.claude/skills/design-status/SKILL.md · 137 lines

How it starts

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

Display the current status of a design loop by reading and parsing the progress tracking file.

Find Progress File

Search for design-review-progress.md in the following locations, in order:

Current working directory
Project root (look for nearest .git directory and check that level)
Any subdirectory — use a glob search like **/design-review-progress.md

If no progress file is found, output:

No active design loop found. Start one with /design-lenses:design-loop <file>

If multiple progress files are found, list all of them with their full paths and ask the user which one they want to inspect. Do not guess.

Parse Progress

Read the progress file and extract structured data from two sections:

From YAML frontmatter, extract these fields:

file — the target file being reviewed
domain — project domain (e.g., motorcycle, e-commerce)
platform — target platform (e.g., Mobile, Desktop, Responsive)
theme — color theme (e.g., Dark, Light)
scope — page scope (e.g., Page, Component, Section)
context — any additional context string
status — one of: in-progress, complete, partial
started — timestamp when the loop began

From the markdown body, parse:

Count all checked [x] checkboxes vs unchecked [ ] checkboxes to determine agent completion
Determine the current iteration by finding the first unchecked agent's iteration group
Extract the list of applied fixes (usually a numbered or bulleted list under a fixes heading)
Extract the summary section content if the loop is complete
Identify iteration names/phases (e.g., DIAGNOSE, FOUNDATIONS, ENHANCE, SHIP)

Display Status

Output a formatted status report based on the parsed data. Follow this structure:

For an in-progress loop:

## Design Loop Status

**File**: path/to/file.html
**Context**: Mobile | Dark theme | Page | motorcycle domain
**Status**: In Progress (Phase 2 of 4: FOUNDATIONS)
**Started**: 2026-03-17 10:00

### Progress
████████░░░░░░░░ 4/8 agents complete (50%)

### Completed
- [x] Iteration 1 — DIAGNOSE
  - Design Critic: 8 issues found, 6 applied
  - Domain Expert: 5 issues found, 4 applied

### In Progress
- [ ] Iteration 2 — FOUNDATIONS
  - Design System Agent: running...
  - Copy & Clarity Agent: pending

### Remaining
- [ ] Iteration 3 — ENHANCE
- [ ] Iteration 4 — SHIP

### Recent Fixes Applied
1. Contrast ratio bumped to WCAG AA (consensus)
2. Focus-visible states added globally (critic, critical)
3. ...

### Estimate
~2 iterations remaining

Read the full file on GitHub · 137 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.

11d ago First seen · 137 lines · 40 tokens per session scan A 8d6f0c3da434

Subscribe to this mod's changes

design-status is a skill published in the GitHub repository andrejkanuch/design-lenses (5 stars, last pushed 5mo ago), licensed MIT. It adds 40 tokens to every session and 1,159 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-31.

Design and UX

webgl-holographic-foil

A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.

nexu-io/open-design · 41 tokens

html-ppt-hermes-cyber-terminal

OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

nexu-io/open-design · 53 tokens

html-ppt-taste-brutalist

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).

nexu-io/open-design · 78 tokens

design-lenses: Skill for Claude Code