impeccable

impeccable is a skill for Claude Code from steve-magne/hookstack. It costs 189 tokens per session (4,586 once invoked), scanned A, a copy of impeccable, MIT.

A set of guidance for designing and improving frontend interfaces, such as websites, dashboards, forms, and app screens. Frontend means the part of software people see and use.

In plain words
What is it for?
Creating, redesigning, reviewing, polishing, or adapting working frontend code.
Why use it?
It gives the agent a defined process for making interface changes and checking the project's existing design rules.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node .claude/skills/impeccable/scripts/pin.mjs <pin|unpin> <command>.

Good fit Creating, redesigning, reviewing, polishing, or adapting working frontend code.

Compare 6 skills from other repositories ↓
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/steve-magne/hookstack
agentmods
npx agentmods add skills/steve-magne/hookstack/impeccable

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 impeccable

README.md
[![agentmods](https://agentmods.dev/badge/skills/steve-magne/hookstack/impeccable/github.svg)](https://agentmods.dev/skills/steve-magne/hookstack/impeccable)
Your own site
<a href="https://agentmods.dev/skills/steve-magne/hookstack/impeccable"><img src="https://agentmods.dev/badge/skills/steve-magne/hookstack/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.

agentmods 80×15 button for impeccable

Your own site · 80×15
<a href="https://agentmods.dev/skills/steve-magne/hookstack/impeccable"><img src="https://agentmods.dev/badge/skills/steve-magne/hookstack/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,586 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 91% 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00189 $0.04586
Opus 5.5 $0.00076 $0.01834
Sonnet 5.5 $0.00038 $0.00917
Haiku 4.5 $0.00019 $0.00459

Measured 1mo ago against content hash 4128333148c9, 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 1mo ago.

The scan reads SKILL.md. This mod also ships 32 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

91% identical to impeccable — 26 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.

.claude/skills/impeccable/SKILL.md · 164 lines

How it starts

The opening of the file, as written. The whole thing — 164 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:

  1. Run node .claude/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.
  2. 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.
  3. 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.
  4. 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.
  5. If the project is brand-new (no existing CSS tokens / theme / committed brand colors found in step 3), run node .claude/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 · 164 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.

  1. 1mo ago First seen · 164 lines · 189 tokens per session scan A 4128333148c9

Subscribe to this mod's changes

impeccable is a skill published in the GitHub repository steve-magne/hookstack (7 stars, last pushed 4d ago), licensed MIT. It adds 189 tokens to every session and 4,586 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to impeccable, differing in 26 lines, and is treated as a copy.

Related

Other skills, from other repositories

ui-ux-pro-max

UI/UX design intelligence expert for web and mobile applications. Use when designing interfaces, selecting color palettes, typography, visual styles, building landing pages, dashboards, or reviewing code for UX issues. Covers 50+ design styles, 97 color palettes, 57 font pairings, 99 UX guidelines, 25 chart types…

shobcoder/shob · 104 tokens

genui

Render structured, glanceable, interactive UI in the chat instead of plain text — dashboards, stat cards, filterable tables, charts, choice panels, forms, quizzes. Panels can carry an id so later turns update them in place, and most interaction resolves in the browser with no round-trip. Read this before calling…

open-octo/octo-agent · 94 tokens

artifact-design

Design guidance for any HTML/Markdown file shown in octo's Artifacts panel — reports, dashboards, architecture/system diagrams, generated UIs, slide-style pages, 3D scenes. Read this BEFORE writing the file, not after — it calibrates how much design effort the request warrants and covers the panel's real constraints…

open-octo/octo-agent · 187 tokens

atomic-visual-options

Planning-phase visual comparison aid. Renders 2-4 side-by-side variants per decision dimension as a single throwaway, self-contained HTML file and captures the user's pick as typed terminal codes (e.g. "A2 B3"). Auto-fires on phrases like "show me a few options", "mock up some variants", "let me see this side by…

damusix/atomic-claude · 150 tokens

vc:tech-graph

Use when you need publish-grade SVG or PNG technical diagrams for architecture, flow, sequence, UML, state, or comparison visuals, with preview used afterward for review rather than generation.

opencue/cuecards · 42 tokens

designmatch

Use when matching a React Native screen to a Claude Design HTML canonical at ≥95% visual parity on real Android/iOS hardware — closes the loop with a VQA stub mode, Playwright canonical renderer at 1080×2444, and a dual-metric pixelmatch + SSIM diff harness producing composite triptychs.

randomittin/heimdall · 69 tokens