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 Dragoon0x/everything-design-taste --skill design-handoffgit clone --depth 1 https://github.com/Dragoon0x/everything-design-tasteWrote 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/dragoon0x/everything-design-taste/design-handoff)<a href="https://agentmods.dev/skills/dragoon0x/everything-design-taste/design-handoff"><img src="https://agentmods.dev/badge/skills/dragoon0x/everything-design-taste/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/dragoon0x/everything-design-taste/design-handoff"><img src="https://agentmods.dev/badge/skills/dragoon0x/everything-design-taste/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.00020 | $0.00318 |
| Opus 5.5 | $0.00008 | $0.00127 |
| Sonnet 5.5 | $0.00004 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
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 1mo 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.
What it actually says
Design Handoff
Handoff Checklist
What Developers Need
- All states designed (default, hover, focus, disabled, loading, error, empty)
- Responsive behavior specified (mobile, tablet, desktop)
- Spacing values (use tokens, not arbitrary pixel values)
- Typography specs (font, size, weight, line-height, color)
- Color values (token names preferred over hex)
- Animation specs (duration, easing, properties)
- Edge cases (long text, no data, many items, error recovery)
- Accessibility notes (focus order, ARIA labels, keyboard behavior)
What Developers Don't Need
- Pixel-perfect mockups of every possible state combination.
- Detailed redlines (modern tools provide inspection).
- A 50-page spec document nobody will read.
Collaboration Model
- Include developers early. Feasibility check during design, not after.
- Pair on complex interactions. Sometimes building together is faster than specifying.
- Design review in browser. Final QA in the actual implementation, not in Figma.
- Shared language. Use design system token names in conversation.
- Fast feedback loops. Small PRs, quick design reviews, iterate.
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.
- 1mo ago First seen · 31 lines · 20 tokens per session scan A f0e68def30e2
design-handoff is a skill published in the GitHub repository Dragoon0x/everything-design-taste (13 stars, last pushed 6mo ago), licensed MIT. It adds 20 tokens to every session and 318 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
antislop-ui
UI and visual skill for antislop. Use when building or editing any interface: color, layout, components, motion. Load with the core.
role-ui-ux-designer
Use when orchestrating UI/UX design systems, anti-AI-slop frontend styling, tactile micro-interactions, responsive design tokens, accessibility standards, and high-fidelity interface engineering.
taste
Anti-slop frontend engineering directive and design taste system. Enforces brief inference, dynamic design dials, absolute prohibition of AI visual tells, and 100% full-output completion.
anti-slop-design
Autonomous Principal Design Technologist. Cures vibe-coded software from AI frontend slop using curated token archetypes and 7-axis quality gating.
scroll-craft
Build premium scroll-driven landing pages for service, product, food, and drink brands. Plan the visitor journey, page grammar, emotional peak, and bespoke signature move. Create dimensional heroes with independent visual planes, restrained motion, and separate mobile composition. Use supplied photos and footage or…
image-to-code
Turn a reference image, screenshot, or mockup into token-driven, accessible code. Infer the design system from the reference (palette, type scale, spacing, radius, layout archetype), map it to the 3-tier tokens, rebuild it, then verify with the kit's gates. Use when the user provides a design/screenshot and wants…