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 vmobifystudio/app-dev-team --skill design-systemgit clone --depth 1 https://github.com/vmobifystudio/app-dev-teamWrote 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/vmobifystudio/app-dev-team/design-system)<a href="https://agentmods.dev/skills/vmobifystudio/app-dev-team/design-system"><img src="https://agentmods.dev/badge/skills/vmobifystudio/app-dev-team/design-system/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/vmobifystudio/app-dev-team/design-system"><img src="https://agentmods.dev/badge/skills/vmobifystudio/app-dev-team/design-system.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.00072 | $0.00579 |
| Opus 5.5 | $0.00029 | $0.00232 |
| Sonnet 5.5 | $0.00014 | $0.00116 |
| Haiku 4.5 | $0.00007 | $0.00058 |
Grade A, and why
design-system 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 1mo 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design system
A design system is not a document, it is a constraint that holds at build time. Tokens nobody is forced to use are a colour list.
Three layers, in this order
- Primitive — the raw values.
blue-600 #2563EB,space-4 16,dur-fast 150ms. No screen ever references a primitive directly. - Semantic — what it means.
text/primary,surface/elevated,semantic/error,motion/enter. Screens reference these and only these. - Component — what a component uses.
button/primary/background→semantic/action.
Skipping layer 2 is the failure: a dark mode, a rebrand or a contrast fix then edits every screen.
The rules
- A hardcoded colour, spacing, radius, duration or font size in a screen is a defect, not a style preference. Name it or use the token that already exists.
- Every semantic token names its dark-mode value at the same time. A token added light-only is a dark-mode bug already merged.
- A new component needs a reason the existing ones cannot compose it. Write the reason in
docs/14-components.md. "It looked different in the mock" is not one. - Every component declares its states — default, pressed, disabled, loading, error, empty where applicable — and its minimum touch target (44pt iOS / 48dp Android).
- Contrast is checked when the token is defined, not when accessibility is audited. Text pairs meet 4.5:1, large text and non-text 3:1. A token failing contrast never ships and is never "fixed downstream".
Extending versus forking
Before adding anything, in this order: use the existing component → extend it with a prop → compose two existing ones → add a new one. Stop at the first that works. The third is where most teams stop too early and the fourth is where design systems die.
Output
Tokens go in docs/13-design-tokens.md, components in docs/14-components.md. Both are single-owner
files — product-designer writes them, everyone reads them. An IC that needs a change asks; it does
not edit.
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.
- 1mo ago First seen · 46 lines · 72 tokens per session scan A f5bd945b638c
design-system is a skill published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 6d ago), licensed MIT. It adds 72 tokens to every session and 579 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
fidelity-gate
Build a UI against a frozen visual reference without drift - an inventory extracted before any code, a relics list, and a gate that MEASURES computed styles on a fixture carrying the reference's own data. Use when a mockup, design spec or screenshot is the contract.
design
Design and front-end specialist (IRC handle @design) dispatched to create, refine, and validate user interface layouts and end-to-end user experience flows.
scroll-craft
Build premium scroll-driven landing pages for service, product, food, and drink brands. Plan the visitor journey, page grammar, emotional peak, and bespoke signature move. Create dimensional heroes with independent visual planes, restrained motion, and separate mobile composition. Use supplied photos and footage or…
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
proto-bot-ops
A workflow for turning an existing application into interface prototypes, implementing approved page changes, and collecting review evidence. It checks the real code, pages, components, data, and visual states instead of treating a design file as an integrated product.
proto-bot-getting-started
A first-conversation guide for starting an interface-prototyping task. It gathers the application, design rules, allowed changes, and preferred delivery format only as needed before producing an initial result.