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.
npx agentmods add skills/ne11nn/cantos-plugin/impeccablenpx skills add ne11nn/cantos-plugin --skill impeccablegit clone --depth 1 https://github.com/ne11nn/cantos-pluginWrote 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/ne11nn/cantos-plugin/impeccable)<a href="https://agentmods.dev/skills/ne11nn/cantos-plugin/impeccable"><img src="https://agentmods.dev/badge/skills/ne11nn/cantos-plugin/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 | $0.00189 | $0.03055 |
| Opus 5 | $0.00095 | $0.01528 |
| Sonnet 5 | $0.00038 | $0.00611 |
| Haiku 4.5 | $0.00019 | $0.00305 |
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.
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
86% identical to impeccable — 75 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 — 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
Before any design work or file edits:
- Load context (PRODUCT.md / DESIGN.md) via the loader script.
- Identify the register and load the matching register reference (brand.md or product.md).
- If the user invoked a sub-command (e.g.
craft,shape,audit), load its reference file too. This is non-negotiable:craftwithoutcraft.mdloaded means you'll skip the shape-and-confirm step the user expects.
Skipping these produces generic output that ignores the project.
1. Context gathering
Two files, case-insensitive. The loader looks at the project root by default and falls back to .agents/context/ and docs/ if the root is clean. Override with IMPECCABLE_CONTEXT_DIR=path/to/dir (absolute or relative to cwd).
- PRODUCT.md: required. Users, brand, tone, anti-references, strategic principles.
- DESIGN.md: optional, strongly recommended. Colors, typography, elevation, components.
Load both in one call:
node .claude/skills/impeccable/scripts/load-context.mjs
Consume the full JSON output. Never pipe through head, tail, grep, or jq. The output's contextDir field tells you where the files were resolved from.
If the output is already in this session's conversation history, don't re-run. Exceptions requiring a fresh load: you just ran /impeccable teach or /impeccable document (they rewrite the files), or the user manually edited one.
/impeccable live already warms context via live.mjs. If you've run live.mjs, don't also run load-context.mjs this session.
If PRODUCT.md is missing, empty, or placeholder ([TODO] markers, <200 chars): run /impeccable teach, then resume the user's original task with the fresh context. If the original task was /impeccable craft, resume into /impeccable shape before any implementation work.
If DESIGN.md is missing: nudge once per session ("Run /impeccable document for more on-brand output"), then proceed.
What ships with it
59 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.
- reference/adapt.md 6.3 KB
- reference/animate.md 7.6 KB
- reference/audit.md 7.1 KB
- reference/bolder.md 6.2 KB
- reference/brand.md 11 KB
- reference/clarify.md 6.0 KB
- reference/codex.md 6.7 KB
- reference/cognitive-load.md 4.7 KB
- reference/color-and-contrast.md 5.6 KB
- reference/colorize.md 7.8 KB
- reference/craft.md 11 KB
- reference/critique.md 17 KB
- reference/delight.md 9.5 KB
- reference/distill.md 5.5 KB
- reference/document.md 28 KB
- reference/extract.md 3.3 KB
- reference/harden.md 8.4 KB
- reference/heuristics-scoring.md 8.6 KB
- reference/interaction-design.md 6.9 KB
- reference/layout.md 7.8 KB
- reference/live.md 50 KB
- reference/motion-design.md 5.6 KB
- reference/onboard.md 7.6 KB
- reference/optimize.md 7.4 KB
- reference/overdrive.md 8.8 KB
- reference/personas.md 6.9 KB
- reference/polish.md 13 KB
- reference/product.md 4.0 KB
- reference/quieter.md 4.7 KB
- reference/responsive-design.md 3.4 KB
- reference/shape.md 11 KB
- reference/spatial-design.md 3.5 KB
- reference/teach.md 9.1 KB
- reference/typeset.md 6.2 KB
- reference/typography.md 8.1 KB
- reference/ux-writing.md 4.2 KB
- scripts/cleanup-deprecated.mjs 8.9 KB runs code
- scripts/command-metadata.json 7.8 KB
- scripts/critique-storage.mjs 8.4 KB runs code
- scripts/design-parser.mjs 25 KB runs code
- scripts/detect-csp.mjs 6.6 KB runs code
- scripts/impeccable-paths.mjs 3.4 KB runs code
- scripts/is-generated.mjs 2.2 KB runs code
- scripts/live-accept.mjs 22 KB runs code
- scripts/live-browser-session.js 3.2 KB runs code
- scripts/live-browser.js 194 KB runs code
- scripts/live-complete.mjs 2.9 KB runs code
- scripts/live-completion.mjs 871 B runs code
- scripts/live-inject.mjs 17 KB runs code
- scripts/live-poll.mjs 7.9 KB runs code
- scripts/live-resume.mjs 1.9 KB runs code
- scripts/live-server.mjs 32 KB runs code
- scripts/live-session-store.mjs 8.8 KB runs code
- scripts/live-status.mjs 1.5 KB runs code
- scripts/live-wrap.mjs 25 KB runs code
- scripts/live.mjs 8.4 KB runs code
- scripts/load-context.mjs 5.0 KB runs code
- scripts/modern-screenshot.umd.js 29 KB runs code
- scripts/pin.mjs 6.0 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.
- 4d ago First seen · 169 lines · 189 tokens per session scan A 61675efdbee2
impeccable is a skill published in the GitHub repository ne11nn/cantos-plugin (1 stars, last pushed yesterday), licensed MIT. It adds 189 tokens to every session and 3,055 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to impeccable, differing in 75 lines, and is treated as a copy.
Other skills, from other repositories
refactoring-the-assembled-ui
Edit, split or share the CSS and JavaScript under plugins/audit/scripts/ui/ — files Python concatenates into one inline and one inline carrying code, in a self-contained page opened over file://. Covers the assembly contract and the byte-level pins in plugins/audit/tests/ that guard it, why the split must be an…
writing-css
How CSS is written in this repo — every value comes from a design token, one component gets one name across both surfaces, and the five theme lints decide what ships. Covers the token layer and the half-finished spacing migration, modern syntax that is actually safe here (cascade layers and container queries are…
frontend-aesthetics
How to make frontends that look genuinely designed instead of generic "AI slop", and how to verify UI work the pipeline can't catch with a test suite. Load whenever a task builds or restyles a user-facing surface — a page, a component, a full redesign, a dashboard, a marketing site. Covers distinctive typography…
eval-ui-ux
Specialized UI/UX evaluator for the Evaluate-Loop. Use this for evaluating UI shell tracks, design system tracks, screen implementation tracks, or any track where the primary deliverable is visual/interactive UI. Checks design system adherence, visual consistency, layout structure, responsive behavior, component…
stream-chain
Stream-JSON chaining for multi-agent pipelines, data transformation, and sequential workflows.
frontend-audit
ProductionOS frontend quality scanner. Auto-activates when editing React/Vue/Svelte components, CSS, or layout files. Checks accessibility, responsive design, performance, and design system consistency.