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/harshii0509/designstack/delightnpx skills add harshii0509/designStack --skill delightgit clone --depth 1 https://github.com/harshii0509/designStackWhat 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.00053 | $0.01963 |
| Opus 5 | $0.00026 | $0.00981 |
| Sonnet 5 | $0.00011 | $0.00393 |
| Haiku 4.5 | $0.00005 | $0.00196 |
Grade A, and why
ds-delight 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Preamble
"../lib/env.sh" "delight"
What this skill does
The best products have moments that make you smile. Not silly — just thoughtful. The "you did it" confetti. The empty state that makes you feel welcomed instead of lost. The little thing that makes your product feel like it was built by someone who cared.
That's what this skill adds.
This skill is for emotional moments, not motion polish across the whole interface. If the user wants broad interaction animation work across existing UI, route them to /ds-animate.
Two focus areas (always start here):
- The success moment — when a user completes something important (submits a form, finishes onboarding, makes their first purchase, creates their first item)
- The first-time experience — when a user arrives for the very first time and sees nothing yet
These two moments have the most impact and the most room to feel special.
"Where do users succeed in your app? Tell me about the moment when they accomplish something — the first time they do the thing your product is built for."
Step 1 — Load the Design Bible vibe
If DESIGN_BIBLE is yes, follow the standard extraction protocol in lib/bible-reader.md. Focus on "The feeling" section.
Let the vibe words guide delight style:
- "calm, focused" → subtle celebration. A gentle color pulse, a quiet checkmark animation. No confetti.
- "warm, approachable" → a friendly success message with warmth. Maybe a small illustrated character. Soft animation.
- "bold, playful" → real celebration. Confetti, color burst, expressive copy. Go for it.
- "professional, minimal" → almost invisible delight. A smooth checkmark, clean success state, precise copy. Restraint is the delight.
Step 2 — Understand their product
Ask:
"Tell me about two moments in your product:
- The success moment — what's the most important thing a user can do? When they finish it, what happens right now? (e.g. 'they submit the form and just get a gray text message')
- The empty moment — when a new user first signs up and there's nothing yet, what do they see? (e.g. 'just a blank list with nothing in it')"
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 · 225 lines · 53 tokens per session scan A d280be3b23ad
ds-delight is a skill published in the GitHub repository harshii0509/designStack (13 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 1,963 once invoked, about $0.0003 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…
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.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
desktop-principles
Desktop-specific UX principles - hover states, pointer precision, keyboard shortcuts, multi-window, focus management. Covers macOS, Windows, Linux, web desktop.
ios-hig-design
Design native iOS interfaces following Apple Human Interface Guidelines. Use when the user mentions "iPhone app", "iPad layout", "SwiftUI", "UIKit", "Dynamic Island", "safe areas", "HIG compliance", "SF Symbols", "haptic feedback", "iOS accessibility", "make my app feel native", or "follow Apple design guidelines".…