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-design-qanpx skills add isaacsight/kernel --skill kernel-chat-design-qagit 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.00073 | $0.00842 |
| Opus 5 | $0.00036 | $0.00421 |
| Sonnet 5 | $0.00015 | $0.00168 |
| Haiku 4.5 | $0.00007 | $0.00084 |
Grade A, and why
kernel-chat-design-qa 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kernel.chat Design QA
Purpose
Prove the page works as a designed publication, not merely as compiling code. Inspect rendered output, exercise interactions, and separate hard failures from craft improvements.
Use this skill after $kernel-chat-web-design. If the problem is conceptual rather than implementation-level, return to $kernel-chat-art-direction. When the user asks for review only, report findings without editing files.
Establish the Review Target
Record:
- Route or file under review
- Local development, production build, or live deployment
- Intended issue identity and core interaction
- Required desktop and mobile widths
- Whether print and standalone artifact filing apply
Do not treat a passing local development route as proof of a production deployment.
Run the Automated Baseline
From the repository root:
node .agents/skills/kernel-chat-design-qa/scripts/audit-page.mjs <url> <output-directory>
The script records desktop and mobile screenshots, document structure, overflow, broken images, undersized controls, runtime errors, reduced-motion activity, and a print proof. It writes audit.json beside the screenshots and exits nonzero on hard runtime failures.
Automated output is evidence, not a design verdict. Open the screenshots and inspect them visually.
Inspect in This Order
- Identity: confirm the page has one legible editorial argument and a recognizable issue silhouette.
- Hierarchy: read the page at thumbnail size, normal size, and 200% zoom. Confirm the eye encounters title, claim, evidence, and navigation in the intended order.
- Responsive composition: compare desktop and mobile as distinct compositions. Check every major section, long heading, bilingual lockup, caption, table, and control.
- Interaction: use keyboard, pointer, and touch-sized viewport. Confirm focus is visible, states are named, controls tell the truth, and content remains understandable without interaction.
- Motion: observe initial load, repeated navigation, fast scrolling, and reduced motion. Confirm the resting page is complete and no essential state depends on animation.
- Media: verify crops, resolution, loading behavior, alt text, poster states, aspect ratios, and that every asset belongs to the same visual grammar.
- Reading quality: check line length, widows, awkward wraps, contrast, caption proximity, density, and the rhythm between compression and release.
- Print and artifact filing: confirm all states remain available in print and standalone artifacts are self-contained when required.
- Production truth: verify the built file exists, the deployed URL resolves, assets load from production paths, and no console or page errors appear live.
What ships with it
2 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 · 71 lines · 73 tokens per session scan A 299f69fa0937
kernel-chat-design-qa is a skill published in the GitHub repository isaacsight/kernel (16 stars, last pushed 3d ago), licensed MIT. It adds 73 tokens to every session and 842 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
aimeat-design-language
The AIMEAT design language in words and in numbers: the two faces (showroom outside, poster inside), the three type tokens every font on the site descends from, the four shapes, the colours, the wordmark, and the one place a value is changed (theme.css tokens) with the map of every surface a token reaches. Use before…
persona-review
Seat a panel of real-distribution-grounded Korean citizen personas in front of a piece of UX, copy, or content and report how ordinary users would react. Samples 5 personas from a catalog, dispatches each as an independent panelist, and synthesizes their reactions. NOT a code/security/performance review (those are…
aibvf-design
Use this skill to generate well-branded interfaces and assets for AI BVF (the AI Business Value Framework, by Craig Horton Advisory), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.
agent-reach
MUST USE when user wants to 调研/research/搜索/search/查/找/look up anything on the internet — e.g. 全网调研 X / 帮我调研一下 X / 查一下 X / 搜搜 X / 看看大家怎么评价 X / X 上有什么讨论 / research this topic。 Also MUST USE when user mentions any platform or shares any URL/链接: 小红书/xiaohongshu/xhs, Twitter/推特/X, B站/bilibili, Reddit, Facebook, Instagram…
gstack-openclaw-office-hours
Use when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any code is written.
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.