A set of instructions for designing and improving frontend interfaces such as websites, dashboards, forms, and app screens. It guides the agent to inspect the existing project context, design system, and relevant code before changing the interface.

Use it to create, redesign, critique, polish, or audit frontend pages and components.

It reduces the risk of making isolated design changes that conflict with the product, existing components, or project conventions.

impeccable — Skill for Codex by asmyshlyaev177/state-in-url

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/asmyshlyaev177/state-in-url

agentmods

npx agentmods add skills/asmyshlyaev177/state-in-url/impeccable

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/asmyshlyaev177/state-in-url/impeccable/github.svg)](https://agentmods.dev/skills/asmyshlyaev177/state-in-url/impeccable)

Your own site

<a href="https://agentmods.dev/skills/asmyshlyaev177/state-in-url/impeccable"><img src="https://agentmods.dev/badge/skills/asmyshlyaev177/state-in-url/impeccable/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/asmyshlyaev177/state-in-url/impeccable"><img src="https://agentmods.dev/badge/skills/asmyshlyaev177/state-in-url/impeccable.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 4,916 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 88% copy Near-identical to another mod 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.00189	$0.04916
Opus 5.5	$0.00076	$0.01966
Sonnet 5.5	$0.00038	$0.00983
Haiku 4.5	$0.00019	$0.00492

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

Security

Grade A, and why

impeccable 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 23d ago.

The scan reads SKILL.md. This mod also ships 29 executable files (scripts/context-signals.mjs, scripts/context.mjs, scripts/critique-storage.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

This is a copy

88% identical to impeccable — 45 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/impeccable/SKILL.md · 169 lines

How it starts

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

Designs and iterates production-grade frontend interfaces. Real working code, committed design choices, exceptional craft.

Setup

You MUST do these steps before proceeding:

Run node .agents/skills/impeccable/scripts/context.mjs once per session. If you've already seen its output in this conversation, do not re-run it. The script either prints the project's PRODUCT.md (and DESIGN.md when present) as a markdown block, or tells you it's missing. Follow whatever it prints. If it reports NO_PRODUCT_MD, stop and follow reference/init.md before doing anything else. If the output ends with an UPDATE_AVAILABLE directive, follow it (ask the user once about updating, then continue). It never blocks the current task.
If the user invoked a sub-command (craft, shape, audit, polish, ...), you MUST read reference/<command>.md next. Non-optional. The reference defines the command's flow; without it you will skip steps the user expects.
Familiarize yourself with any existing design system, conventions, and components in the code. Read at least one project file (CSS / tokens / theme / a representative component or page). Required even when you've loaded a sub-command reference in step 2. Don't reinvent the wheel; use what's there when it works, branch out when the UX wins.
Read the matching register reference. This is non-optional; skipping it produces generic output. If the project is marketing, a landing page, a campaign, long-form content, or a portfolio (design IS the product), read reference/brand.md. If it is app UI, admin, a dashboard, or a tool (design SERVES the product), read reference/product.md. Pick by first match: (1) task cue ("landing page" vs "dashboard"); (2) surface in focus (the page, file, or route being worked on); (3) register field in PRODUCT.md.
If the project is brand-new (no existing CSS tokens / theme / committed brand colors found in step 3), run node .agents/skills/impeccable/scripts/palette.mjs to receive a brand seed color and composition guidance. This is the anchor for your primary brand color. Compose the rest of the palette (bg, surface, ink, accent, muted) around it per the script's instructions. Use OKLCH throughout. Skip this step only if step 3 found committed brand colors in existing tokens; in that case identity-preservation wins.

Read the full file on GitHub · 169 lines

Files

What ships with it

60 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.

23d ago First seen · 169 lines · 189 tokens per session scan A cd90f6b3e7d2

Subscribe to this mod's changes

impeccable is a skill published in the GitHub repository asmyshlyaev177/state-in-url (418 stars, last pushed 21d ago), licensed MIT. It adds 189 tokens to every session and 4,916 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to impeccable, differing in 45 lines, and is treated as a copy.

CSS and styling Design and UX Frontend client-components nextjs query-params react-hooks reactjs state-management

kiranism-shadcn-dashboard

Guide for building features, pages, tables, forms, themes, and navigation in this Next.js 16 shadcn dashboard template. Use this skill whenever the user wants to add a new page, create a feature module, build a data table, add a form, configure navigation items, add a theme, set up RBAC access control, or work with…

Kiranism/next-shadcn-dashboard-starter · 142 tokens

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…

mastra-ai/mastra · 77 tokens

design-system

Design system consistency checks and token guidance for Mantine-based UI.

design-sparx/mantine-analytics-dashboard · 16 tokens

design

Design workflow that creates design systems, DESIGN.md, and design tokens with anti-pattern enforcement and accessibility checks.

first-fluke/fullstack-starter · 22 tokens

ui-beats

Use this skill when users want to add, customize, or troubleshoot UI Beats components in React/Next.js projects. It covers component selection, shadcn registry installation from uibeats.com, the UI Beats MCP server, motion and reduced-motion handling, and integration patterns for animated sections.

nikhils4/ui-beats · 62 tokens

korrodesign

Design Copilot with two enforcement layers (Taste Guardian + Blind Spot ESLint plugin, 14 rules). Works standalone with zero dependencies. 7-phase design pipeline. Produces Awwwards-level websites with automated UI hygiene enforcement.

KorroAi/korrodesign · 50 tokens