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 atretyak1985/swarmery --skill design-acquiregit clone --depth 1 https://github.com/atretyak1985/swarmeryWrote 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-acquire)<a href="https://agentmods.dev/skills/atretyak1985/swarmery/design-acquire"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/design-acquire/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-acquire"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/design-acquire.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.00069 | $0.01866 |
| Opus 5 | $0.00034 | $0.00933 |
| Sonnet 5 | $0.00014 | $0.00373 |
| Haiku 4.5 | $0.00007 | $0.00187 |
Grade A, and why
design-acquire 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 7d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Phase 1 of design-implement. Four input shapes arrive in practice, and they do not promise
the same thing: only a self-contained HTML export is ground truth for geometry. This skill
turns whatever arrived into a path plus an honest statement of what that path can support, and
hands both back. It does not extract tokens (Phase 2) and it does not measure anything
(design-verify).
The export route in Claude Design
This is the part operators do not find on their own — reproduce it for them exactly:
In Claude Design (claude.ai/design) open the project → the Share menu in the top right corner → the Export section → then either Claude Code — "Implement this design in code" → Send (sends the handoff prompt into the Claude Code session), or Project HTML → Download (downloads a
.zipwith self-contained HTML/CSS). Pixel work needs Project HTML specifically: the handoff prompt describes intent, while the.zipcontains what actually renders.
Input shape 1 — a handoff prompt
The operator pasted a design tool's handoff prompt (or it arrived through Send).
- Parse it. Look for a reference to a file or a URL carrying the actual markup.
- If the prompt leads to HTML — fetch it and continue with shape 2. The prompt's prose is context, not a substitute.
- If it does not — ask for
Project HTMLand show the route above. A handoff prompt on its own describes intent: it states what the screen means, not the computed values it renders at, so nothing downstream can be measured against it.
Promises: intent and structure. Not geometry, not exact values.
Input shape 2 — a .zip or .html export
- Unpack into the working directory:
.design-verify/source/<slug>/. - Find the entry document (the top-level
index.html, or the single.htmlat the root of the archive; if several are plausible, list them and let the operator pick — do not guess which screen is meant). - Check self-containment: scan for external network resources (remote stylesheets, webfonts, images, script tags pointing off-host). Record every one of them. They change what renders, so they change the measurement — a font fetched from the network that fails to load in the headless run silently reshapes every text block.
- Pass the entry document's path forward.
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.
- 7d ago First seen · 157 lines · 69 tokens per session scan A 1c146da1e95f
design-acquire is a skill published in the GitHub repository atretyak1985/swarmery (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 69 tokens to every session and 1,866 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
excalidraw
Create or extend editable Excalidraw diagrams from descriptions or repository evidence using a local skeleton-to-scene converter.
multi-surface-render
Multi-surface rendering with json-render — one JSON spec produces React web, Next.js, React Native, Ink terminal UIs, PDFs, emails, Remotion videos, OG images, and 3D scenes. Covers renderer target selection, registry mapping, and platform APIs (renderToBuffer, renderToStream, renderToFile). Use when generating output…
web-artifacts-builder-v2
Suite of tools for creating elaborate, multi-component claude.ai HTML artefacts using modern frontend web technologies (React 19, Tailwind CSS v4, shadcn/ui). Use for complex artefacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artefacts.
design-workflow
A workflow for bringing design handoff files, design tokens, and project design briefs into a code project. It validates the tokens and loads research, system, and specification notes before interface implementation.
cosmic
Futuristic sci-fi aesthetic with dark themes, vibrant neon accents, and immersive spatial elements.
modern
Contemporary editorial style with serif typography, minimal palettes, and clean layouts for polished digital products.