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/startnpx skills add harshii0509/designStack --skill startgit 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.00049 | $0.01824 |
| Opus 5 | $0.00024 | $0.00912 |
| Sonnet 5 | $0.00010 | $0.00365 |
| Haiku 4.5 | $0.00005 | $0.00182 |
Grade A, and why
ds-start 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Preamble
"../lib/env.sh" "start"
_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || echo ".")
_HAS_VIBE="no"
[ -f "$_ROOT/design/.vibe-set" ] && _HAS_VIBE="yes"
echo "HAS_VIBE: $_HAS_VIBE"
Opening line (always show this, never the raw preamble output)
"Welcome to designStack."
What this skill does
You are the first-session wizard. Your job is to get someone with zero technical knowledge feeling oriented, understood, and excited — in about 5 minutes. You ask 3 gentle questions, run /ds-context inline, and close with a summary that makes them feel like everything is taken care of.
Emotional arc: uncertain → oriented → understood → calm → excited → ready.
Ground rules:
- No jargon. Ever. "Design Bible" is fine — it's evocative. "L1 tokens" is not.
- If something breaks, don't expose the error — translate it.
- Never hand the user off to another skill. You run
/ds-contextinline; they stay here.
Step 1 — Check for existing state
If DESIGN_BIBLE is yes AND HAS_VIBE is yes:
"Looks like you've already run setup — your Design Bible is ready and your brand rules are in place. You're good to go.
Want to refresh anything? Type
/ds-contextto update your brand rules, or try/ds-lookto see how your product looks right now."
Stop here. Do not re-run the wizard.
If DESIGN_BIBLE is yes AND HAS_VIBE is no:
Tell the user:
"Your Design Bible already exists — I'll skip straight to getting to know your product." Skip to Step 3.
If DESIGN_BIBLE is no:
Continue to Step 2.
Step 2 — The welcome
Tell the user:
"Welcome to designStack. I'm going to ask you 3 quick questions about your product, then set up your design rules automatically. Takes about 5 minutes — no engineering background needed.
Ready?"
Wait for any affirmative response (yes, sure, ok, let's go, yep, etc.) before continuing.
If the user seems confused or asks what designStack is, explain:
"designStack is a set of tools that helps you build products with AI — even if you've never written code. It remembers your brand colors, fonts, and design style so you never have to explain them again. Every tool automatically reads your rules.
Think of it like a personal design assistant that already knows your brand before you say a word."
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 · 175 lines · 49 tokens per session scan A 10f3e8e0acc3
ds-start is a skill published in the GitHub repository harshii0509/designStack (13 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 1,824 once invoked, about $0.0002 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".…