agentmods.dev

impeccable

impeccable is a skill for Claude Code, Codex from abhinavteja123/codemore. It costs 189 tokens per session (4,916 once invoked), scanned A, a copy of impeccable, MIT.

A workflow for designing, reviewing, and improving frontend screens and components, such as websites, dashboards, forms, and onboarding. It works with the project's existing design files and code.

In plain words
What is it for?
Use it to create or refine frontend pages, audit an interface, improve visual consistency, clarify content, and adapt or animate existing UI elements.
Why use it?
It provides a structured way to find unclear layouts, inconsistent styles, and other interface problems while making changes in working code.

Skill for Claude CodeCodex

not rated 2 1mo ago A scan 189 tokens copy · 88% MIT
View the source file abhinavteja123/codemore
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.

agentmods
npx agentmods add skills/abhinavteja123/codemore/impeccable
Any agent
npx skills add abhinavteja123/codemore --skill impeccable
Clone the repo
git clone --depth 1 https://github.com/abhinavteja123/codemore

Made for: Claude Code, 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 impeccable

README.md
[![agentmods](https://agentmods.dev/badge/skills/abhinavteja123/codemore/impeccable.svg)](https://agentmods.dev/skills/abhinavteja123/codemore/impeccable)
Your own site
<a href="https://agentmods.dev/skills/abhinavteja123/codemore/impeccable"><img src="https://agentmods.dev/badge/skills/abhinavteja123/codemore/impeccable.svg" alt="Measured on agentmods" 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. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00189 $0.04916
Opus 5 $0.00095 $0.02458
Sonnet 5 $0.00038 $0.00983
Haiku 4.5 $0.00019 $0.00492

Measured 4d ago against content hash cd90f6b3e7d2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 4d 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:

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

  1. 4d 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 abhinavteja123/codemore (2 stars, last pushed 1mo ago), licensed MIT. It adds 189 tokens to every session and 4,916 once invoked, about $0.0009 per session on Opus 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.

Design and UXFrontendai-agentscode-qualitydeveloper-toolsgithub-actionsmcpsast
Related

Other skills, from other repositories

skylos-security

Investigate and harden Skylos security behavior. Use when the user asks to validate a security finding, reproduce a scanner bypass, assess false negatives, review LLM evidence filters, analyze CI/cloud policy trust boundaries, classify severity, or add regression tests for security-sensitive analyzer behavior.

duriantaco/skylos · 61 tokens

skylos

Run, interpret, or modify Skylos safely. Use when the user asks to scan code with Skylos, explain SKY- findings, triage dead-code false positives, audit security/secrets/SCA/LLM behavior, update Skylos rules/docs/CI, benchmark analyzer behavior, or change this repository safely.

duriantaco/skylos · 67 tokens

setup-config

Analyze a repository and generate an intelligent omen.toml with project-specific defaults. Use when starting Omen in a new project.

panbanda/omen · 28 tokens

track-trends

Analyze repository health trends over time using historical git commits. Use for quarterly reports, release retrospectives, or tracking technical debt paydown progress.

panbanda/omen · 32 tokens

assess-impact

Analyze blast radius before changing specific files. Use before refactoring core components, making breaking API changes, or modifying shared code to identify affected files and stakeholders.

panbanda/omen · 35 tokens

audit-architecture

Audit module coupling, cohesion, hidden dependencies, and design smells. Use when conducting architecture reviews, evaluating design decisions, or identifying structural tech debt.

panbanda/omen · 33 tokens