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 agentmods add skills/volomydyr/design-engineer-plugin/dev-component-gallerynpx skills add volomydyr/design-engineer-plugin --skill dev-component-gallerygit clone --depth 1 https://github.com/volomydyr/design-engineer-pluginWrote 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/volomydyr/design-engineer-plugin/dev-component-gallery)<a href="https://agentmods.dev/skills/volomydyr/design-engineer-plugin/dev-component-gallery"><img src="https://agentmods.dev/badge/skills/volomydyr/design-engineer-plugin/dev-component-gallery.svg" alt="Measured on agentmods" 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 | $0.00083 | $0.02019 |
| Opus 5 | $0.00042 | $0.01009 |
| Sonnet 5 | $0.00017 | $0.00404 |
| Haiku 4.5 | $0.00008 | $0.00202 |
Grade A, and why
dev-component-gallery 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 3d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component Gallery Skill
A single-page visual gallery of every component in the project. Every variant, all in one viewport, with source paths labelled – so duplicates are obvious, gaps are visible, and visual quality is auditable. Inspired by Yana's yananaaas.github.io reference (pill-tab navigation across categories, real components rendered with production styles, source attribution per entry).
Purpose
Two specific problems the gallery solves:
- Visual redundancy detection. When Claude tends to create five new versions of an existing component, a side-by-side gallery makes the duplicates obvious. Two cards rendering identical buttons but pointing to
Button.tsxandPrimaryButton.tsxare the redundancy signal. - Visual quality assurance. Code-level inspection works but lacks visual clarity. Storybook works but is a docs site, not a canvas. The gallery is closer to a design canvas: one viewport, all components, real production styles.
Stack-agnostic flow
The skill never carries a hardcoded "framework → location" table. The plugin works for every stack – iOS, Android, Flutter, SwiftUI, Compose, web frameworks not yet invented – so the skill adapts on each invocation.
Step 1: Read existing config
Read .design-engineer-plugin/config.yaml. If gallery.path is already set (from a previous run on this project), jump to step 4 with the persisted location.
Step 2: Detect stack
Use existing detection infrastructure:
- The environment summary already produced by
skills/meta-setup/scripts/detect-environment.sh(run during/design-engineer:launch). - Targeted file presence checks for stack markers:
package.json– read framework name + version (next, vue, svelte, astro, vite + react/vue, etc.)Package.swift– Swift / SwiftUIpubspec.yaml– Flutter / Dartbuild.gradle/build.gradle.kts– Android (Jetpack Compose)Cargo.toml– Rust / Tauri / Yew / Leptos*.csproj/MAUImarkers – .NET MAUIindex.html+ custom-element script tags – vanilla web-components stack (Yana's case)- Static-site markers – Jekyll, Hugo, Eleventy, Astro static
- Identify the primary UI framework. If multi-target (e.g., Tauri app with React inside), pick the layer the components live in.
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.
- 3d ago First seen · 137 lines · 83 tokens per session scan A 948907e5545b
dev-component-gallery is a skill published in the GitHub repository volomydyr/design-engineer-plugin (19 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 2,019 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…