Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/SZoloth/skill-packnpx agentmods add skills/szoloth/skill-pack/design-swarmWrote 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/szoloth/skill-pack/design-swarm)<a href="https://agentmods.dev/skills/szoloth/skill-pack/design-swarm"><img src="https://agentmods.dev/badge/skills/szoloth/skill-pack/design-swarm/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/szoloth/skill-pack/design-swarm"><img src="https://agentmods.dev/badge/skills/szoloth/skill-pack/design-swarm.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.00074 | $0.01775 |
| Opus 5 | $0.00037 | $0.00888 |
| Sonnet 5 | $0.00015 | $0.00355 |
| Haiku 4.5 | $0.00007 | $0.00178 |
Grade A, and why
design-swarm 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 9d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Swarm
Orchestrate 10 specialized design agents — each embodying a different skill/lens — to run holistic audits, ideation sessions, and implementations in parallel.
Orchestration Flow
When invoked, follow these steps exactly:
1. Parse Arguments
Extract from the invocation:
- Modes: One or more of
audit,ideate,implement(default:auditif none specified) - Target: The thing to evaluate — one of:
- Screenshot path (
.png,.jpg,.webp) - URL (
http://orhttps://) - File path (code file)
- Text brief (quoted description of an interface)
- Screenshot path (
2. Detect Target Type
| Signal | Type | Notes |
|---|---|---|
.png, .jpg, .webp, .gif |
screenshot | Read the image directly |
http://, https:// |
url | Use browser tools to snapshot the page |
| Existing file path | code | Read the file(s) |
| Everything else | brief | Treat as text description |
3. Load Orchestration Context
Read these files:
modules/orchestrator.md— synthesis logic, conflict resolution, final report templatereferences/scoring-rubric.md— universal 1-10 scalereferences/agent-weights.md— default weights for composite scoring
4. Create Team
TeamCreate(team_name: "design-swarm", description: "Holistic design audit/ideation/implementation")
5. Execute Phases
For each requested mode, in order (audit → ideate → implement):
Phase: Audit
-
Determine participating agents (see orchestrator.md Phase Gating):
- Screenshot-only: skip
baseline-ui - Code-only: all 10
- URL: all 10 (snapshot first, then inspect code if accessible)
- Brief: all 10 (theoretical assessment)
- Screenshot-only: skip
-
Create tasks via TaskCreate — one per participating agent
-
Spawn agents in parallel via Task tool. For each agent:
a. Read the agent template:
modules/agents/<agent-name>.mdb. Read the source knowledge file(s) listed in the template's "Source Knowledge" section c. Construct the agent prompt by combining:- The full agent template (structure + evaluation criteria)
- The full source knowledge content
- The target context (screenshot/URL snapshot/code/brief)
- Mode: "audit"
- The scoring rubric content
- Instructions to mark task complete and send report via SendMessage to "team-lead"
What ships with it
13 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.
- modules/agents/accessibility.md 3.3 KB
- modules/agents/baseline-ui.md 2.6 KB
- modules/agents/composition.md 2.5 KB
- modules/agents/craft-philosophy.md 2.7 KB
- modules/agents/critique.md 2.9 KB
- modules/agents/foundations.md 2.5 KB
- modules/agents/frontend-design.md 2.6 KB
- modules/agents/interaction.md 2.5 KB
- modules/agents/interface-craft.md 2.7 KB
- modules/agents/motion.md 3.2 KB
- modules/orchestrator.md 4.6 KB
- references/agent-weights.md 1.3 KB
- references/scoring-rubric.md 1.1 KB
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.
- 9d ago First seen · 170 lines · 74 tokens per session scan A 9e4dbf2b4dc2
design-swarm is a skill published in the GitHub repository SZoloth/skill-pack (14 stars, last pushed 5mo ago), licensed MIT. It adds 74 tokens to every session and 1,775 once invoked, about $0.0004 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
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.
prototype
Build a self-contained local prototype at .turbo/prototypes/ .html, drive it, and hand it to the user to settle unknowns that prose cannot answer. Use when the user asks to "prototype this", "build a prototype", "mock this up", "show me what it would look like", "let me try the interaction first", or when a decision…
user-experience
Apply a UX lens to a user-facing change: whether it serves the user's real goal and whether the path through it holds together, using the Understanding, Bridging, and Flowing contexts. Use when scoping, planning, or assessing any change that affects what a user sees or does. Loaded as a lens during planning and…
svg-art
Generates artistic SVGs directly as code — minimal line icons, geometric marks, generative patterns, or hand-drawn compositions — and assembles a modern 2026 HTML gallery preview. Saves each session to its own semantically named folder on the Desktop. Learns from feedback: which styles you loved, which compositions…
ux-interview
Plays the role of a real user in an interview-style usability test. Takes context about the product (URL, description, focus areas), auto-suggests a persona (overridable), then drives real Chrome via the claude-in-chrome extension to explore the product think-aloud style — narrating live reactions while flagging…
shipkit-ux-audit
Use when auditing implemented UI for missing UX patterns. Triggers: 'audit UX', 'check UX', 'missing patterns', 'UX gaps'.