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 sanky369/vibe-building-skills --skill design-foundationgit clone --depth 1 https://github.com/sanky369/vibe-building-skillsWrote 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/sanky369/vibe-building-skills/design-foundation)<a href="https://agentmods.dev/skills/sanky369/vibe-building-skills/design-foundation"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/design-foundation/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/sanky369/vibe-building-skills/design-foundation"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/design-foundation.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.00151 | $0.02108 |
| Opus 5 | $0.00076 | $0.01054 |
| Sonnet 5 | $0.00030 | $0.00422 |
| Haiku 4.5 | $0.00015 | $0.00211 |
Grade A, and why
design-foundation 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 13d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Foundation
Produce a working tokens file for this specific codebase — not a document about tokens. A token is a named design decision (--color-text-primary, --space-4); centralizing them is what makes every later design skill (layout, type, color, components) land consistently. Governing principle: extract before you invent — in an existing codebase, the token system should formalize the best of what's already there, so migration is renaming, not redesigning.
When to use / handoffs
- Use to create tokens from scratch or extract them from an existing codebase.
- If the user's pain is specifically color (palette, contrast, dark mode depth) →
skills/frontend-design/color-systemafter the token skeleton exists. - If specifically type (scale, fonts, readability) →
skills/frontend-design/typography-system. - If they want components built on tokens →
skills/frontend-design/component-architecturenext. - For broad "where do I start" requests →
skills/frontend-design/frontend-orchestrator.
Step 1 — Inspect the codebase
Before asking anything, gather evidence:
- Find the current styling entry points. Glob
tailwind.config.{js,ts,cjs,mjs},**/globals.css,**/index.css,**/app.css,**/*theme*,**/tokens*. Read them. - Detect the stack. Tailwind v4 (
@import "tailwindcss"+@themein CSS) vs v3 (config filethemeobject) vs CSS Modules / styled-components / vanilla CSS. Checkpackage.jsonfor the tailwindcss version. - Measure drift. Grep source for
#[0-9a-fA-F]{3,8}\b,rgba?\(,hsla?\(→ count distinct colors. Grep for\d+pxand Tailwind arbitrary values\[(\d+px|#)→ count rogue spacing/size values. These counts go in your rationale. - Find the de facto system. Sort found values by frequency. The most-used font sizes, spacing steps, and colors are the candidate tokens.
- Check dark mode (
dark:,prefers-color-scheme) — determines whether the semantic layer must ship two modes now.
Step 2 — Intake
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.
- 13d ago First seen · 126 lines · 151 tokens per session scan A 4ae2f48a1325
design-foundation is a skill published in the GitHub repository sanky369/vibe-building-skills (30 stars, last pushed 2mo ago), licensed MIT. It adds 151 tokens to every session and 2,108 once invoked, about $0.0008 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
core-components
Core component library and design system patterns. Use when building UI, using design tokens, or working with the component library.
web-design-reviewer
This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage…
ui-web
Web UI - glassmorphism, Tailwind, dark mode, accessibility.
mulmoterminal-theme
Build a colour scheme of your own for MulmoTerminal — one that joins Midnight, Nord, Daylight and Solarized in Settings' theme picker and can then be pinned per project. Writes themes in /.mulmoterminal/config.json, the whole-app palette (panels, borders, accent, text), which has no UI for creating one — Settings only…
ijfw-ui-spec
Use when the user says: 'ui spec', 'design contract', 'ui audit setup', 'lock the design', 'visual contract', 'ui review setup', or '/ijfw-ui-spec'. Produces UI-SPEC.md as the visual design contract before any frontend or visual-artifact build, and dispatches ijfw-ui-auditor as the final 6-pillar gate.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use when the user asks to build landing pages, websites, dashboards, web components, or any frontend UI. Generates creative, polished code that avoids generic AI aesthetics.