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/dnsatgit/aigod/impeccablenpx skills add dnsatgit/aigod --skill impeccablegit clone --depth 1 https://github.com/dnsatgit/aigodWhat 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.00018 | $0.00695 |
| Opus 5 | $0.00009 | $0.00347 |
| Sonnet 5 | $0.00004 | $0.00139 |
| Haiku 4.5 | $0.00002 | $0.00069 |
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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Impeccable Frontend Constraint Layer
This is NOT an optional skill — it is a mandatory constraint applied to all frontend output. Any sub-agent or skill producing HTML, CSS, or JavaScript UI code must comply.
Based on: https://github.com/pbakaus/impeccable
Enforcement
When any agent produces frontend code, this constraint layer is automatically loaded. The output must pass the audit pipeline:
/audit → /normalize → /harden → /polish → /critique
The 7 Standards
1. Typography
- No Inter, Roboto, or system-ui defaults without explicit justification
- Modular type scale (e.g., 1.25 ratio)
- 16px minimum body text
- Line height: 1.4-1.6 for body, 1.1-1.2 for headings
- Max line length: 65-75 characters
2. Color (OKLCH)
- Use OKLCH color space, not hex/rgb/hsl
- Tinted neutrals — no pure gray (#808080)
- 60-30-10 color ratio (dominant-secondary-accent)
- Semantic color tokens (not raw values in components)
3. Spatial System (4pt base)
- All spacing values are multiples of 4px
- Use
gapovermarginfor component spacing - Container queries over media queries where supported
- Consistent padding scale
4. Motion
- Meaningful transitions only — no decorative animation
- Respect
prefers-reduced-motion - Duration: 150-300ms for micro-interactions, 300-500ms for layout shifts
- No bounce easing, no elastic effects
5. Interaction
- 44px minimum touch targets
- Visible focus indicators (not just outline: none)
- Hover states that also work on touch
- Loading states for async operations
6. Responsive
- Mobile-first approach
- Fluid typography with clamp()
- Logical CSS properties (margin-inline, padding-block)
- i18n budget: 30-40% extra space for translated text
7. Accessibility
- WCAG AA minimum: 4.5:1 contrast for body text, 3:1 for large text and UI
- Semantic HTML elements
- ARIA labels only when semantic HTML is insufficient
- Screen reader testing checklist
Anti-Patterns (Auto-Fail)
Any of these in the output = automatic failure:
What ships with it
1 file 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.
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.
- 2d ago First seen · 91 lines · 18 tokens per session scan A 45e6b45fd416
impeccable is a skill published in the GitHub repository dnsatgit/aigod (2 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 695 once invoked, about $0.0001 per session on Opus 5. 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
design-guide
Paperclip UI design system guide for building consistent, reusable frontend components. Use when creating new UI components, modifying existing ones, adding pages or features to the frontend, styling UI elements, or when you need to understand the design language and conventions. Covers: component creation, design…
Shade ShadCN install
Guardrails for running pnpm dlx shadcn@latest add in Shade — never overwrite existing components, fresh branch first, swap raw colours for semantic tokens after integrating. Trigger when the user proposes a shadcn add, or when a fresh ShadCN-shaped file lands in apps/shade/src/components/ui.
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…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
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…
obsidian-layout-adjustment
Workflow for working with the user on changing how Obsidian looks using CSS snippets. Use this whenever the user asks to restyle Obsidian, tune a vault's visual layout, adjust tabs, sidebars, note surfaces, properties, backlinks, graph panes, file explorer rows, icons, links, shadows, active states, or CSS snippets.…