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 pro-vi/designer --skill designer-loopgit clone --depth 1 https://github.com/pro-vi/designerWrote 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/pro-vi/designer/designer-loop)<a href="https://agentmods.dev/skills/pro-vi/designer/designer-loop"><img src="https://agentmods.dev/badge/skills/pro-vi/designer/designer-loop/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/pro-vi/designer/designer-loop"><img src="https://agentmods.dev/badge/skills/pro-vi/designer/designer-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00081 | $0.03667 |
| Opus 5.5 | $0.00032 | $0.01467 |
| Sonnet 5.5 | $0.00016 | $0.00733 |
| Haiku 4.5 | $0.00008 | $0.00367 |
Grade A, and why
designer-loop 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designer Loop
The human is the designer. Claude Design has taste. The orchestrating agent is translation + plumbing — not a co-designer.
Three layers, each with its own job:
- Human: taste. Describes intent, reacts to variants in their own words.
- Claude Design (via the
designerMCP): aesthetic judgment. Produces variants, names them, wires tweaks. - Orchestrator (this agent): translates intent to a minimal faithful prompt, presents what Claude produced, interprets reactions, promotes the result to code.
Don't muddle the three.
When NOT to invoke this skill
For trivial mechanical changes — single token, single value, no feeling-shaped question ("set --border-radius: 12px", "make the bg darker by 1 stop", "add 8px of padding here") — just make the change directly. Don't boot the MCP. Don't propose variants. Show the diff and move on.
This skill is for feeling-shaped, exploratory, or multi-dimensional design work.
The Loop
1. Intent → Human describes what they want to feel/change (not specific values)
2. Read → Agent calls designer_session; reads adjacent code/tokens if relevant
3. Relay → Agent translates intent into a minimal prompt; sends via designer_prompt
4. Taste → Human reacts to the variants Claude produced (in the tasting harness)
5. Interpret → Agent translates reaction into next prompt or promotion
6. Repeat 3-5 → Until human says "that's it"
7. Promote → designer_handoff; bundle's chat transcript is the decision record
Phase 1: Intent
The human speaks in feelings, not values.
Good intent: "The sidebar feels heavy — I want it to recede." "I want an intake screen that doesn't feel clinical."
Bad intent (if it appears): --border-radius: 12px — already a solution, not this skill's job.
Interview only when intent is genuinely unclear, and only about scope — never about aesthetics.
Scope questions (yours to ask): what data is rendered, what the primary user action is, what failure modes must be visible, what the adjacent screens are, what must NOT change.
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 · 218 lines · 81 tokens per session scan A f529c8beb527
designer-loop is a skill published in the GitHub repository pro-vi/designer (62 stars, last pushed 3d ago), licensed MIT. It adds 81 tokens to every session and 3,667 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-08-30.
Other skills, from other repositories
webgl-holographic-foil
A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
glance-canonical-layouts
Use this skill to create home screen widgets using Jetpack Glance Canonical Layouts from the Android Platform Samples project, or when asked to implement standard widget layout patterns (including Check List, Image Grid, Snap Scrolling, and Standard Toolbar).
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.