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 varutasu/agent-pipeline --skill design-systemsgit clone --depth 1 https://github.com/varutasu/agent-pipelineWrote 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/varutasu/agent-pipeline/design-systems)<a href="https://agentmods.dev/skills/varutasu/agent-pipeline/design-systems"><img src="https://agentmods.dev/badge/skills/varutasu/agent-pipeline/design-systems/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/varutasu/agent-pipeline/design-systems"><img src="https://agentmods.dev/badge/skills/varutasu/agent-pipeline/design-systems.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.00000 | $0.02593 |
| Opus 5 | $0.00000 | $0.01296 |
| Sonnet 5 | $0.00000 | $0.00519 |
| Haiku 4.5 | $0.00000 | $0.00259 |
Grade A, and why
design-systems 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 8d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: design-systems description: >- Audit or design a component/token/governance system. Produces a maturity assessment + concrete recommendations across token architecture, component hierarchy, governance, and adoption metrics. Use when role-design-system- auditor is invoked, when the user asks "is our design system any good" or "how do we ship a DS", when patterns recur across audits (see design-critique step 9), or when teams are duplicating primitives. Skip for server-only convoys (skip flag: design-system).
Design systems
Audit + design framework for component-and-token systems. Covers token architecture (3-tier W3C format), component hierarchy (Atomic Design), governance models (centralized / federated / hybrid), and a maturity model for benchmarking. Outputs an audit report scored against a 5-stage maturity rubric, plus concrete recommendations.
This skill answers two distinct questions:
- Auditing an existing system: where's the leverage to invest next?
- Designing a new system: what's the minimum viable scope to start, what's deferred?
When to invoke
- Automatic: by
role-design-system-auditorwhen a convoy ships a new component, modifies a primitive, or touchestailwind.config.{ts,js}/tokens/**/theme/**. - Manual: when the user says "audit our design system", "ship a design system", "why are buttons inconsistent", "set up design tokens".
- Pattern-triggered: when
design-critiqueoraccessibility-auditflags a recurring pattern (DS-level finding) 3+ times across audits. - Adoption review: when launching a new app/surface that should consume the system.
What ships with it
2 files 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.
- 8d ago First seen · 199 lines · 0 tokens per session scan A b332fc503000
design-systems is a skill published in the GitHub repository varutasu/agent-pipeline (2 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,593 tokens. 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 skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…