Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add atretyak1985/swarmery/plugin install design-packWrote 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/atretyak1985/swarmery/design-build)<a href="https://agentmods.dev/skills/atretyak1985/swarmery/design-build"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/design-build/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/atretyak1985/swarmery/design-build"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/design-build.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.00162 | $0.03661 |
| Opus 5.5 | $0.00065 | $0.01464 |
| Sonnet 5.5 | $0.00032 | $0.00732 |
| Haiku 4.5 | $0.00016 | $0.00366 |
Grade A, and why
design-build 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Six phases that carry a screen from "here is a design" to "here is a measured diff". Each phase has exactly one output, and the next phase does not start until that output exists.
Two rules hold the whole workflow up: the token inventory comes from a real headless render, never from reading the design's CSS by eye; and completion is a number plus an image, never an impression.
This document is the procedure only. Input shapes and what each one can promise live in
design-acquire; the measurement procedure lives in design-verify; the precision rules
live in references/fidelity-checklist.md and the named failure modes in
references/anti-patterns.md. Nothing here repeats them.
Step 0 — Prerequisites
0.1 — Read ${CLAUDE_PROJECT_DIR}/.claude/project.json, the design block.
Required: design.tokensFile, design.componentsRoot, design.routesRoot, design.devUrl,
design.verify (both verify.lint and verify.typecheck).
If the block is missing, or any required field is empty, stop loudly. Name the specific fields that are not filled in — not "the config is incomplete", but the list of them — and say where the form is: the project dashboard → plugins → design-pack. Do not guess a path, do not infer a components root from a directory listing, do not run on a partial block.
Optional fields and their defaults:
| Field | Default | Read by |
|---|---|---|
design.fontLoader |
— | Phase 3 font check (next-font | link-tag | self-hosted | none) |
design.devCommand |
— | Phase 6, when design.devUrl does not answer |
design.diff.threshold |
0.5 |
Phase 6 verdict |
design.diff.pixelTolerance |
0.1 |
Phase 6 per-pixel comparison |
design.budget.maxIterations |
4 |
Phase 5 correction loop cap |
design.budget.maxFiles |
12 |
Phase 4 sanity cap on the approved file list |
0.2 — Read the project's CLAUDE.md in full, before any edit. In a large repository that
file carries the decision history that changes how a screen is built — which layer owns
styling, which component library is already committed to, what is deliberately not abstracted.
Skipping it produces work that is locally correct and architecturally wrong.
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.
- 1mo ago First seen · 282 lines · 162 tokens per session scan A 8e7d943df04d
design-build is a skill published in the GitHub repository atretyak1985/swarmery (7 stars, last pushed yesterday), licensed Apache-2.0. It adds 162 tokens to every session and 3,661 once invoked, about $0.0006 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-19.
Other skills, from other repositories
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
web-animation-design
Design and implement web animations that feel natural and purposeful. Use this skill proactively whenever the user asks questions about animations, motion, easing, timing, duration, springs, transitions, or animation performance. This includes questions about how to animate specific UI elements, which easing to use…
design-context-extract
Extract design DNA from app screenshots, live URLs, or screen recordings using Google Stitch — color palettes, typography, spacing tokens, component patterns, and motion specs as design-tokens.json or Tailwind config. Use when the user points to a screenshot, URL, or video and asks to extract or audit the design…
figma-design-handoff
Figma-to-code design handoff patterns including Figma Variables to design tokens pipeline, component spec extraction, Dev Mode inspection, Auto Layout to CSS Flexbox/Grid mapping, and visual regression with Applitools. Use when converting Figma designs to code, documenting component specs, setting up design-dev…
animation-motion-design
Animation and motion design patterns using Motion library (formerly Framer Motion) and View Transitions API. Use when implementing component animations, page transitions, micro-interactions, gesture-driven UIs, or ensuring motion accessibility with prefers-reduced-motion.
aceternity-ui
100+ animated React components (Aceternity UI) for Next.js with Tailwind. Use for hero sections, parallax, 3D effects, or encountering animation, shadcn CLI integration errors.