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 commands/volomydyr/design-engineer-plugin/helpgit clone --depth 1 https://github.com/volomydyr/design-engineer-pluginWhat 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.00020 | $0.00788 |
| Opus 5 | $0.00010 | $0.00394 |
| Sonnet 5 | $0.00004 | $0.00158 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
design-engineer:help 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 2d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Engineer Plugin – Help
Present this information to the user. Do not modify the text – show it as written.
A plugin for Claude Code that walks you through building a product, start to finish. Think of it as a swiss knife for product design. It packs a full methodology into one tool – research, psychology, prototyping, development – but stays easy to pick up. You run one command, it figures out where you are, and opens the right instrument.
Commands
| Command | What it does |
|---|---|
/design-engineer:launch |
Detects your situation – setup, resume, or capability guide |
/design-engineer:discovery |
Runs the design workflow – discovery, strategy, planning, validation |
/design-engineer:prototype |
Generates clickable HTML prototypes from an idea, planning docs, or existing designs |
/design-engineer:development |
Development workflow – CLAUDE.md, agent pipeline, context management, TDD, implementation |
/design-engineer:review |
Reviews your work – visual quality, accessibility, psychology (100+ principles), design system, ethics |
/design-engineer:document |
Saves decisions, learnings, and project state. Auto-purges disposable working files at every phase boundary. Helps communicate with stakeholders |
/design-engineer:stop |
Save progress and pause mid-activity – pick up later with /design-engineer:launch |
/design-engineer:tidy |
Manual purge of disposable working files under .design-engineer-plugin/temporary/ (Playwright debug captures, intermediate drafts, scratch). Use before commit, or anytime the working tree feels noisy |
/design-engineer:help |
This help screen |
You only need to remember /design-engineer:launch. It guides you to everything else.
Modes
Most commands work in two ways:
- Guided mode – step-by-step with approval at every stage. The AI explains its thinking, shows findings one at a time, and waits for your input at each step.
- Autopilot – autonomous with minimal input. The AI plans and executes, then shows you the results. Faster but you review after, not during.
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.
- 2d ago First seen · 60 lines · 20 tokens per session scan A d72cc219a654
design-engineer:help is a command published in the GitHub repository volomydyr/design-engineer-plugin (19 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 788 once invoked, about $0.0001 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 commands, from other repositories
profile
Save, load, inspect, update, reset, or delete diagram-design client profiles.
buildable-design
Create a UI/UX design brief from a prompt or the current Buildable app spec.
mockup-analyze
Extract design specifications from HTML mockups using AI vision.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
overlay
The spatial overlay — a click-through canvas floating over every window that both you and agents can draw on. /overlay shows status; /overlay open launches it (⌃⌥⌘D toggles draw mode, esc leaves); /overlay post --rel X,Y,W,H puts an arrow / box / highlight / spotlight / label / callout / sticker on the screen from an…
excalidraw-export
Export the current Excalidraw canvas scene, element set, library, or theme by retrieving the live resource snapshot.