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/looknpx skills add harshii0509/designStack --skill lookgit 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.00052 | $0.02231 |
| Opus 5 | $0.00026 | $0.01115 |
| Sonnet 5 | $0.00010 | $0.00446 |
| Haiku 4.5 | $0.00005 | $0.00223 |
Grade A, and why
ds-look 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Preamble
"../lib/env.sh" "look"
What this skill does
Check if your site actually looks like it should. You point me at a page, I take a screenshot, compare it against your Design Bible (colors, fonts, spacing, brand rules), and give you a plain-English report with an annotated image showing exactly where things are off.
This skill never changes code — it only looks and reports.
This is the single-page check. If the user wants a scan across many pages, route them to /ds-brand. If they want a final pre-launch checklist, route them to /ds-polish.
Step 1 — Load the Design Bible
If DESIGN_BIBLE is yes, read the Bible file fully. Follow the standard extraction protocol in lib/bible-reader.md. Extract:
- L1 colors (primary, background, text, accent)
- L1 typography (font families, sizes, weights)
- L1 spacing scale
- L1 border radius rules
- L4 component rules (buttons, cards, forms, nav)
- Memory Log (recent changes, known intentional decisions)
If DESIGN_BIBLE is no:
"I don't have your design rules yet, so I can't compare this page against your brand rules. I'll still look for layout issues and obvious problems. Want me to set up your Design Bible first? Run
/ds-context— it takes 5 minutes and makes every future check much smarter."
Continue the check either way.
Step 2 — Get the URL
Ask the user:
"What page should I check? Give me the URL — e.g.
http://localhost:3000orhttps://your-site.com/dashboard. If you have a specific part in mind (like the signup flow or the pricing page), tell me that too."
If the user already mentioned a URL in the conversation, use that and confirm:
"I'll check [URL] — is that the right page?"
Step 3 — Take a screenshot (if browse available)
If BROWSE is not NOT_FOUND:
"../lib/visual-audit.sh" screenshot "<URL>" "look" "before"
$B text
If the URL is not reachable, run and show the output of:
"../lib/visual-audit.sh" not_running
Do not continue until the user confirms the project is running.
What ships with it
1 file 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 · 242 lines · 52 tokens per session scan A 8a985fe44175
ds-look is a skill published in the GitHub repository harshii0509/designStack (13 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 2,231 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…
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".…
taiyi-ui-design
TaiyiForge 第 4 阶段 — UI/UX 契约，产出 UI-DESIGN.md。四端通用。.