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/isaacsight/kernel/kernel-chat-web-designnpx skills add isaacsight/kernel --skill kernel-chat-web-designgit clone --depth 1 https://github.com/isaacsight/kernelWhat 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.00071 | $0.02197 |
| Opus 5 | $0.00036 | $0.01099 |
| Sonnet 5 | $0.00014 | $0.00439 |
| Haiku 4.5 | $0.00007 | $0.00220 |
Grade A, and why
kernel-chat-web-design 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kernel Chat Web Design
Overview
This skill encodes the visual grammar, interaction constraints, styling tokens, and publishing guidelines of kernel.chat. It serves as the single source of truth for creating editorial magazine issues that honor the POPEYE-inspired warmth while remaining calm, accessible, and scientifically honest.
Skill Routing
Use this skill as the implementation and publication contract. Pair it with the specialist that matches the phase:
- Use
$kernel-chat-art-directionbefore implementation when the visual concept, cover, composition, type hierarchy, asset grammar, or responsive transformation is not yet resolved. - Use
$motion-design,$micro-interactions, or the relevant GSAP skill when motion requires detailed choreography beyond the house constraints below. - Use
$kernel-chat-design-qaafter implementation for rendered desktop/mobile inspection, accessibility and motion checks, print proof, and live-production verification.
Do not collapse these phases into a single styling pass. Art direction decides the visual argument; this skill implements it in the house system; design QA proves the result.
The House Grammar
kernel.chat is an editorial magazine, not an application. Every release is named ISSUE N · MONTH YEAR.
Voice & Copy Constraints
- Never name the inspiration on the site. No mention of "POPEYE" in user-visible copy. Homage is carried entirely through grammar.
- Magazine terminology only. Use terms like issue, feature, spread, folio, kicker, monument, colophon, masthead, dateline, bulletin. Do not use app terms like dashboard, panel, card, widget, modal.
- Typography. EB Garamond for prose, Courier Prime for metadata, Noto Serif JP for Japanese subtitles and parallel text.
- Bilingual Lockups. EN-primary with selective JP subtitles/lockups (
.pop-bilingual > .pop-latin / .pop-jp). - No Emojis. Use the star/asterisk symbol (★) as the single recurring folio system glyph.
What ships with it
7 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.
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 · 136 lines · 71 tokens per session scan A fc8559b23539
kernel-chat-web-design is a skill published in the GitHub repository isaacsight/kernel (16 stars, last pushed 3d ago), licensed MIT. It adds 71 tokens to every session and 2,197 once invoked, about $0.0004 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-30.
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…
design-taste-frontend-v1
The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is design-taste-frontend (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.
material-ui-styling
Chooses the right Material UI styling approach (sx, styled, theme overrides, global CSS) from official MUI guidance. Use when styling @mui/material components, customizing themes, overriding slots, or comparing sx vs styled.
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.