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.
git clone --depth 1 https://github.com/ssheleg/sheleg-design-skillWrote 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/commands/ssheleg/sheleg-design-skill/sheleg-design)<a href="https://agentmods.dev/commands/ssheleg/sheleg-design-skill/sheleg-design"><img src="https://agentmods.dev/badge/commands/ssheleg/sheleg-design-skill/sheleg-design/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/commands/ssheleg/sheleg-design-skill/sheleg-design"><img src="https://agentmods.dev/badge/commands/ssheleg/sheleg-design-skill/sheleg-design.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.00016 | $0.00648 |
| Opus 5.5 | $0.00006 | $0.00259 |
| Sonnet 5.5 | $0.00003 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
sheleg-design 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 5d 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
Invoke the sheleg-design skill and apply it to the current request.
- Read the skill's
SKILL.mdfirst, then — before designing anything — its full referenceSHELEG_DESIGN.mdand, before any animation,MOTION_DOCTRINE.md(same directory).SHELEG_DESIGN.mdsays how motion is built; the doctrine says whether to build it at all. Skipping the second is how a keyboard path ends up animated. - Task: $ARGUMENTS — if empty, ask what page or section to build/upgrade.
- If the arguments name a style pack, use that pack without re-asking. The
thirty-nine packs are
instrument-console,editorial-luxury,workbench,briefing-room,atrium,babylove,patchbay,nameplate,rimlight,onionskin,deskmate,test-drive,surveyor,chorus,outrank,orchard,field-notes,cyclorama,showroom,blueprint,prism,maquette,scoreboard,datasheet,manpage,pigeonhole,roster,ora,tenor,paperclip,ledger,awning,router,daylight,notation,almanac,vitrine,proscenium,bulletin. Otherwise pick per theSKILL.mdtable, and say which pack you picked and why before you build. - Set the three dials out loud before any layout exists —
DESIGN_VARIANCE,MOTION_INTENSITY,VISUAL_DENSITY, with one line of reasoning. TheSKILL.md"Reading them off the brief" table gives the starting values; baseline is7 / 5 / 4. Announcing them and then drifting is the failure this step exists to prevent. - Then proceed per the skill's "How to Apply" order.
- Product UI (dashboard, admin, internal/dev tool, design tokens, theming):
apply a standalone pack and its token CSS — no scroll clock, no particle
field, no cinematic motion.
workbenchis the default;field-notesis the fork for a developer product sold on auditability, andbriefing-roomfor a deck published as a page. The packs state the distinction; read it rather than defaulting. - AI surfaces (chat, agent runs, streaming, generated content): read
AI_PRODUCT_PATTERNS.mdas well. - Follow the skill's non-negotiables (Quick Reference table) and ship every layer's reduced-motion/fallback branch in the same commit.
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.
- 5d ago Changed · -30 tokens per session ad33684b1e76
- 1mo ago First seen · 35 lines · 46 tokens per session scan A 8914a7d687d8
sheleg-design is a command published in the GitHub repository ssheleg/sheleg-design-skill (4 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 648 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-08-31.
Other commands, from other repositories
dashboard-layout
Design and build a complete dashboard layout — sidebar navigation, KPI cards, chart areas, data tables, filter bar, and responsive behavior. Outputs production-ready HTML/CSS.
style-guide
Generate a style guide with design tokens, type scale, spacing, components, and Tailwind or CSS config.
add-library
Kullanıcı "kütüphane ekle", "library ekle", "tasarım sistemi ekle", "design system ekle" dediğinde bu komutu uygula.
ds-remove
Kullanıcı "kütüphane kaldır", "library sil", "DS'i kaldır", "DS'i sil", "tasarım sistemini kaldır" dediğinde bu komutu uygula. Kullanıcı eski/yanlış eklenmiş bir DS'in cache'ini ve state'ini temizlemek ister.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.