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.
git clone --depth 1 https://github.com/klimentij/klimkitnpx agentmods add skills/klimentij/klimkit/klimkit-impeccableWrote 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.
[](https://agentmods.dev/skills/klimentij/klimkit/klimkit-impeccable)<a href="https://agentmods.dev/skills/klimentij/klimkit/klimkit-impeccable"><img src="https://agentmods.dev/badge/skills/klimentij/klimkit/klimkit-impeccable.svg" alt="Measured on agentmods" height="20"></a>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.00192 | $0.05317 |
| Opus 5 | $0.00096 | $0.02658 |
| Sonnet 5 | $0.00038 | $0.01063 |
| Haiku 4.5 | $0.00019 | $0.00532 |
Grade A, and why
klimkit-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 6d 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.
This is a copy
89% identical to impeccable — 36 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.
How it starts
The opening of the file, as written. The whole thing — 182 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.mjsonce 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 reportsNO_PRODUCT_MD, stop and followreference/init.mdbefore doing anything else. If the output ends with anUPDATE_AVAILABLEdirective, 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 readreference/<command>.mdnext. 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), readreference/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)registerfield 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.mjsto 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.
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.
- agents/impeccable_asset_producer.toml 8.1 KB
- agents/impeccable_manual_edit_applier.toml 6.9 KB
- agents/openai.yaml 235 B
- reference/adapt.md 9.9 KB
- reference/animate.md 10 KB
- reference/audit.md 7.1 KB
- reference/bolder.md 6.4 KB
- reference/brand.md 10 KB
- reference/clarify.md 10 KB
- reference/codex.md 6.8 KB
- reference/colorize.md 13 KB
- reference/craft.md 12 KB
- reference/critique.md 39 KB
- reference/delight.md 9.6 KB
- reference/distill.md 5.6 KB
- reference/document.md 27 KB
- reference/extract.md 3.4 KB
- reference/harden.md 8.4 KB
- reference/init.md 13 KB
- reference/interaction-design.md 6.4 KB
- reference/layout.md 8.5 KB
- reference/live.md 55 KB
- reference/onboard.md 7.6 KB
- reference/optimize.md 7.4 KB
- reference/overdrive.md 8.9 KB
- reference/polish.md 13 KB
- reference/product.md 3.7 KB
- reference/quieter.md 4.8 KB
- reference/shape.md 11 KB
- reference/typeset.md 14 KB
- scripts/cleanup-deprecated.mjs 8.9 KB runs code
- scripts/command-metadata.json 7.8 KB
- scripts/context-signals.mjs 7.9 KB runs code
- scripts/context.mjs 9.7 KB runs code
- scripts/critique-storage.mjs 8.8 KB runs code
- scripts/design-parser.mjs 25 KB runs code
- scripts/detect-csp.mjs 6.6 KB runs code
- scripts/detect.mjs 620 B runs code
- scripts/detector/browser/injected/index.mjs 67 KB runs code
- scripts/detector/cli/main.mjs 9.5 KB runs code
- scripts/detector/detect-antipatterns-browser.js 188 KB runs code
- scripts/detector/detect-antipatterns.mjs 1.6 KB runs code
- scripts/detector/engines/browser/detect-url.mjs 8.6 KB runs code
- scripts/detector/engines/regex/detect-text.mjs 23 KB runs code
- scripts/detector/engines/static-html/css-cascade.mjs 33 KB runs code
- scripts/detector/engines/static-html/detect-html.mjs 8.9 KB runs code
- scripts/detector/engines/visual/screenshot-contrast.mjs 6.4 KB runs code
- scripts/detector/findings.mjs 363 B runs code
- scripts/detector/node/file-system.mjs 6.7 KB runs code
- scripts/detector/profile/profiler.mjs 4.4 KB runs code
- scripts/detector/registry/antipatterns.mjs 17 KB runs code
- scripts/detector/rules/checks.mjs 98 KB runs code
- scripts/detector/shared/color.mjs 4.4 KB runs code
- scripts/detector/shared/constants.mjs 4.1 KB runs code
- scripts/detector/shared/page.mjs 252 B runs code
- scripts/impeccable-paths.mjs 3.8 KB runs code
- scripts/is-generated.mjs 2.2 KB runs code
- scripts/live-accept.mjs 26 KB runs code
- scripts/live-browser-session.js 3.2 KB runs code
- scripts/live-browser.js 342 KB runs code
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.
- 6d ago First seen · 182 lines · 192 tokens per session scan A 0e5c8ffbb336
klimkit-impeccable is a skill published in the GitHub repository klimentij/klimkit (7 stars, last pushed 27d ago), licensed MIT. It adds 192 tokens to every session and 5,317 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to impeccable, differing in 36 lines, and is treated as a copy.
Other skills, from other repositories
extract-design-system
Extract design primitives from a public website and generate starter token files for your project.
make-interfaces-feel-better
Use when building or reviewing UI polish: typography, hit areas, nested radius, optical alignment, shadows, media outlines, micro-interactions, and animation performance.
frontend-skill
Use when the task asks for a visually strong landing page, website, app, prototype, demo, or game UI. This skill enforces restrained composition, image-led hierarchy, cohesive content structure, and tasteful motion while avoiding generic cards, weak branding, and UI clutter.
artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Use whenever the task produces or modifies anything a user will see rendered — websites, landing pages, web apps, dashboards, React/HTML/Vue components, artifacts with visual output, style overhauls, or "make this…
frontend-design
Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly.