impeccable

A frontend design add-on with one skill and 23 commands for reviewing and improving interface design. Frontend development is the part of an application that users see and interact with.

In plain words
What is it for?
Polishing, auditing, and critiquing frontend work, plus detecting the listed design anti-patterns.
Why use it?
It gives developers named checks and actions for finding design problems and recognised anti-patterns in web interfaces.

Plugin for Claude Code

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 plugins/pbakaus/impeccable/plugin
Claude Code
/plugin marketplace add pbakaus/impeccable
Clone the repo
git clone --depth 1 https://github.com/pbakaus/impeccable

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin 89% copy Near-identical to another mod in the catalogue.
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 2d 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.

Origin

This is a copy

89% identical to impeccable — 2 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.

plugin/.claude-plugin/plugin.json · 13 lines

What it actually says

{
  "name": "impeccable",
  "description": "Design fluency for frontend development. 1 skill with 23 commands (/impeccable polish, /impeccable audit, /impeccable critique, etc.) and curated anti-pattern detection.",
  "version": "4.1.2",
  "author": {
    "name": "Paul Bakaus",
    "email": "[email protected]"
  },
  "homepage": "https://impeccable.style",
  "repository": "https://github.com/pbakaus/impeccable",
  "skills": "./skills/"
}
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. 2d ago First seen · 13 lines scan A 7597c0f2cd92

Subscribe to this mod's changes

impeccable is a plugin published in the GitHub repository pbakaus/impeccable (64,510 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. It is 89% identical to impeccable, differing in 2 lines, and is treated as a copy.