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 skills add oalders/kitchen-sink --skill implement-design-handoffgit clone --depth 1 https://github.com/oalders/kitchen-sinkWrote 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/oalders/kitchen-sink/implement-design-handoff)<a href="https://agentmods.dev/skills/oalders/kitchen-sink/implement-design-handoff"><img src="https://agentmods.dev/badge/skills/oalders/kitchen-sink/implement-design-handoff/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/oalders/kitchen-sink/implement-design-handoff"><img src="https://agentmods.dev/badge/skills/oalders/kitchen-sink/implement-design-handoff.svg" alt="Reviewed on agentmods" width="80" 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.00088 | $0.03323 |
| Opus 5 | $0.00044 | $0.01662 |
| Sonnet 5 | $0.00018 | $0.00665 |
| Haiku 4.5 | $0.00009 | $0.00332 |
Grade A, and why
implement-design-handoff 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 8d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Design Handoff
Overview
Wiring a design-system handoff — a rendered component/card export from a design tool — into an app's real templates and stylesheet is a recurring, stack-agnostic task with a recurring set of failure modes. The mistakes are predictable, and the ordering of the steps is what prevents them.
Core principle: the rendered card is the source of truth for appearance, and you are not done until you have put the rendered result beside the design, property by property. A diff looks clean while shipping an oval logo, a search field mashed against the brand, nav links the design shows but the page hid, and a wordmark bolded that the design renders plain. Every one of those is obvious in a five-second side-by-side and invisible in the diff. This skill forces that side-by-side and orders the steps so the cheap mistakes die first.
When to Use
Use when:
- Implementing a design handoff / component export into real templates and CSS
- "Build this design", "apply the design handoff", wiring
*.card.htmlcards + component source into an app - Writing a GitHub issue that points a later implementing agent at a design (the second mode below)
Skip when:
- Greenfield UI with no design-tool export to reproduce faithfully
- Pure logic/data changes with no visual surface
The Failure Modes (what this skill prevents)
The same handoffs fail the same ways, every time:
- Trusting the handoff's prose/README over the rendered card.
- Approximating colors and spacing by eye instead of using the real tokens.
- Restyling a shared partial/component that feeds more than one page, silently changing pages the handoff never mentioned.
- Fighting the screenshot/preview tooling and giving up on visual verification.
- Two defects that pass functional tests and screenshots yet still miss the design: character-level text drift (smart vs straight quotes, decorative wrapping glyphs, punctuation, casing, ellipsis) and orphaned input bindings (an input the form still collects but the redesign renders nowhere).
- The costliest: declaring it done before ever putting the rendered result beside the design.
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.
- 8d ago First seen · 152 lines · 88 tokens per session scan A c91037d14832
implement-design-handoff is a skill published in the GitHub repository oalders/kitchen-sink (4 stars, last pushed 8d ago), licensed MIT. It adds 88 tokens to every session and 3,323 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-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…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
reveal-hover-effect
Build cursor-following spotlight reveals that expose a second aligned image through a soft radial mask. Use for hover-to-color, before-and-after, x-ray, material, texture, product-detail, and illustrated hero effects where a desaturated or embossed base image should remain visible while another treatment follows an…
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…
better-colors
Helps you build a color system and answer anything about color in your project. You can generate palettes, use semantic tokens, convert between formats, check contrast and more.