Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/adilkalam/orca/impeccable-hub)<a href="https://agentmods.dev/skills/adilkalam/orca/impeccable-hub"><img src="https://agentmods.dev/badge/skills/adilkalam/orca/impeccable-hub.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.00000 | $0.04281 |
| Opus 5 | $0.00000 | $0.02141 |
| Sonnet 5 | $0.00000 | $0.00856 |
| Haiku 4.5 | $0.00000 | $0.00428 |
Grade A, and why
impeccable-hub 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.
How it starts
The opening of the file, as written. The whole thing — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Impeccable — the design hub
This is the ONE home for durable design knowledge. Every design verb (/impeccable --craft,
--typeset, --colorize, --layout, --bolder, --harden, …) loads this hub, so the aesthetic is
present structurally — you never need it re-stated.
This hub POINTS; it does not inline. The banned rules, voice anchors, preferences, and detector rules each
have a single canonical home under docs/concepts/design-contract/. Re-inlining them here would
recreate the lossy monolith this system was built to delete (#POISON_PATH). Read the source files when
you reach for the corresponding move — they carry the full voice, regex signals, and substitutes.
Path note: in this repo the collection lives at
docs/concepts/...; deployed it lives at~/.claude/docs/concepts/.... Both resolve to the same content. Read whichever exists.
1. The felt-state baseline (the spine)
Start every interface from the felt state of the person, not the task. This is the
interfaces-that-feel practice — it is the first thing you load.
→ skills/interfaces-that-feel/SKILL.md (the full practice: felt-state framing, motion craft,
copy voice, empty states, error messages, loading, onboarding, micro-interactions).
Technical correctness is the floor. The ceiling is: does this product know the user is a person?
2. The aesthetic — voice anchors (the user's own words)
The voice anchors are load-bearing direct quotes from Adil. They are the why behind every refusal and
move below. Do not paraphrase or dilute them; edits that weaken them must be refused (#POISON_PATH).
→ docs/concepts/design-contract/voice-anchors.md — the full anchor set (17 anchors).
→ docs/concepts/design-contract/persona.md — the POSITIVE side of the aesthetic (taste, references, gravity).
The anchors and banned rules say what is refused; the persona says what is aimed at — the flatness mission,
context-over-reflex, the named references, the composition discipline (entry point / pace /
density-per-moment). Read it before composing any new surface — FORWARD seeds draw from it at bind
time. Judgment + gravity, never a house style; anti-convergence outranks it. (Pointer — the content
lives in the file, not here.)
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 · 259 lines · 0 tokens per session scan A 2f8e2a9ab2c6
impeccable-hub is a skill published in the GitHub repository adilkalam/orca (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,281 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…
moai-ref-ui-polish
UI polish and interface-completion reference: the small visual details — concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas — that separate polished interfaces from generic ones. Agent-extending skill that amplifies…