design-audit

design-audit is a skill for Codex from Kappaemme-git/codex-design-audit-skill. It costs 107 tokens per session (2,728 once invoked), scanned A, original, MIT.

A structured review of a website, web app, landing page, or frontend that scores its design and lists evidence-based issues and fixes.

In plain words
What is it for?
Checking layout, visual hierarchy, user experience, mobile behavior, accessibility, perceived performance, wording, and frontend polish.
Why use it?
It turns a broad visual or usability review into clear priorities instead of a list of subjective comments.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions Codex.

Good fit Checking layout, visual hierarchy, user experience, mobile behavior, accessibility, perceived performance, wording, and frontend polish.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kappaemme-git/codex-design-audit-skill/design-audit
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.

Any agent
npx skills add Kappaemme-git/codex-design-audit-skill --skill design-audit
Clone the repo
git clone --depth 1 https://github.com/Kappaemme-git/codex-design-audit-skill

Made for: Codex.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/kappaemme-git/codex-design-audit-skill/design-audit.svg)](https://agentmods.dev/skills/kappaemme-git/codex-design-audit-skill/design-audit)
Your own site
<a href="https://agentmods.dev/skills/kappaemme-git/codex-design-audit-skill/design-audit"><img src="https://agentmods.dev/badge/skills/kappaemme-git/codex-design-audit-skill/design-audit.svg" alt="Measured on agentmods" height="20"></a>
Per session 107 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,728 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.00107 $0.02728
Opus 5 $0.00053 $0.01364
Sonnet 5 $0.00021 $0.00546
Haiku 4.5 $0.00011 $0.00273

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

Security

Grade A, and why

design-audit 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.

design-audit/SKILL.md · 297 lines

How it starts

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

Design Audit

Overview

Use this skill to inspect a website or frontend surface and produce a practical design audit: evidence, scores, concrete issues, and prioritized fixes. Prefer direct inspection of the running page whenever possible.

Use re-audit mode when the user asks to compare before/after, check improvements, re-run the audit after fixes, or verify whether a previous audit's issues were solved.

Language

Match the user's language for the entire audit. Support English and Italian explicitly.

  • If the user writes in Italian, write headings, table labels, statuses, priorities, verdicts, category notes, and fix sections in Italian.
  • If the user writes in English, write the audit in English.
  • If the user mixes languages, use the dominant language of the request.
  • Keep preset IDs unchanged (landing-page, saas-dashboard, etc.) so prompts and comparisons remain stable.
  • Keep standard frontend terms in English when they are clearer or commonly used: CTA, focus state, keyboard navigation, layout shift, responsive, mock, hero, dashboard.

Italian label mapping:

  • Overall -> Sintesi
  • Scorecard -> Griglia
  • Category Notes -> Note per Categoria
  • Top Issues -> Problemi Principali
  • Recommended Fixes -> Fix Consigliati
  • Quick wins -> Fix Veloci
  • Medium work -> Interventi Medi
  • Deeper work -> Interventi Strutturali
  • Re-Audit -> Rivalutazione
  • Score Delta -> Delta Punteggi
  • Fix Verification -> Verifica Fix
  • Verification notes -> Note di Verifica
  • Remaining Priorities -> Priorità Rimaste
  • Next Fix Pass -> Prossimo Giro di Fix
  • What works -> Cosa funziona
  • What hurts -> Cosa penalizza
  • Fix -> Fix
  • Priority -> Priorità
  • Confidence -> Confidenza
  • Verdict -> Verdetto
  • Excellent -> Eccellente
  • Good -> Buono
  • Needs work -> Da migliorare
  • Weak -> Debole
  • Critical -> Critico
  • High -> Alta
  • Medium -> Media
  • Low -> Bassa
  • Fixed -> Risolto
  • Improved -> Migliorato
  • Still open -> Ancora aperto
  • Regressed -> Peggiorato

Read the full file on GitHub · 297 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 8d ago First seen · 297 lines · 107 tokens per session scan A 81a750d0e011

Subscribe to this mod's changes

design-audit is a skill published in the GitHub repository Kappaemme-git/codex-design-audit-skill (47 stars, last pushed 4mo ago), licensed MIT. It adds 107 tokens to every session and 2,728 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-30.

Related

Other skills, from other repositories

chakra-ui-builder

Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…

chakra-ui/chakra-ui · 214 tokens

frontend-visual-qa

Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…

daymade/claude-code-skills · 145 tokens

prototype-web

A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.

nexu-io/html-anything · 24 tokens

animation-principles

Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.

Owl-Listener/designer-skills · 59 tokens

refactoring-ui

Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…

wondelai/skills · 132 tokens

ue-component-model

Create or edit the Universal Editor component configuration (component-definition.json, component-models.json, component-filters.json) for AEM Edge Delivery Services blocks. Use this skill whenever the user mentions component models, component definitions, component filters, block configuration for the Universal…

adobe/skills · 140 tokens