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 notque/vexjoy-agent --skill jev-designgit clone --depth 1 https://github.com/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/jev-design)<a href="https://agentmods.dev/skills/notque/vexjoy-agent/jev-design"><img src="https://agentmods.dev/badge/skills/notque/vexjoy-agent/jev-design/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/notque/vexjoy-agent/jev-design"><img src="https://agentmods.dev/badge/skills/notque/vexjoy-agent/jev-design.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.00046 | $0.01701 |
| Opus 5.5 | $0.00018 | $0.00680 |
| Sonnet 5.5 | $0.00009 | $0.00340 |
| Haiku 4.5 | $0.00005 | $0.00170 |
Grade A, and why
jev-design 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 today.
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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jev design
Each part of the work goes to whoever does it best:
| Phase | Who | Output |
|---|---|---|
| 1. Brief | the agent running the skill | brief.json |
| 2. Pick | Jev, through scripts/plan.py |
a component per requirement, a style recipe, install commands, and CSS |
| 3. Compose and build | the agent, with the frontend skill |
layout, hierarchy, copy, custom parts, and working code |
| 4. Review | the agent, with any screenshot tool | concrete findings, then fixes or a revised brief |
Jev only picks from lists: a component from the catalog's candidates and a recipe from its styles. It does not write layout, copy, or code. The agent does all open-ended work. Everything below is a default. Override any step when you have a stated reason, and write the reason in your summary.
1. Brief
Turn the user's request into brief.json. Read references/brief-writing.md for the procedure and a worked example.
{"brief":"Support agents triage 200+ cases a day on desktop; calm, dense, keyboard-first.",
"style_traits":["dense","calm","professional"],
"requirements":[
{"id":"results","role":"Compare, filter, and act on open cases","capabilities":["tabular-data","filter","row-actions"]},
{"id":"details","role":"Inspect one case without leaving the list","capabilities":["overlay","details"]}
]}
- List capabilities, style traits, recipes, and limits with
--list-capabilities. Use only listed names. - Keep the brief to audience, task, and tone, 1,500 characters at most. Layout and copy notes stay with you for phase 3.
- Add
"primitives": "radix" | "base" | "aria"when the project already uses one primitive set. - Ask the user only when the surface type (landing page or app) or the audience is unknown. Otherwise decide, and record the assumption.
2. Pick
python3 skills/frontend/jev-design/scripts/plan.py \
--input brief.json --output /tmp/design-plan.json \
--receipt /tmp/jev-design-receipt.json --css /tmp/design-theme.css
What ships with it
8 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.
- today Changed · +1 lines abc90754c92d
- 23d ago Changed · +51 lines · +8 tokens per session 5bab8d90ff80
- 25d ago First seen · 42 lines · 38 tokens per session scan A 4f185cc5352d
jev-design is a skill published in the GitHub repository notque/vexjoy-agent (442 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 1,701 once invoked, about $0.0002 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-09-22.
Other skills, from other repositories
frontend-ui-design
Use when design and build production-grade UI components using React, Vue, or vanilla HTML/CSS. Create responsive layouts, design systems, and accessible interfaces. Use when designing and build production-grade ui components using react, vue, or.
radix-primitives
Use when radix UI headless primitives — accessible, unstyled React components for dialogs, dropdowns, tooltips. Use when working with radix primitives.
shadcn-ui
Use when shadcn/ui component library — copy-paste React components, Tailwind CSS, Radix primitives, theming. Use when working with shadcn ui.
material-ui
Use when material UI (MUI) React components — theming, styled engine, data grid, date pickers, icons. Use when working with material ui.
unlayer-integration
Integrates Unlayer's email, page, popup, and document builders into web applications through React, Vue, Angular, or plain JavaScript. Use for builder component setup, props, editor access patterns, and multiple instances. For the standalone Image Editor or @unlayer/react-image-editor, use unlayer-image-editor.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Covers design thinking, typography pairing, color theory, motion design, spatial composition, and code quality. Generates real working code — HTML/CSS/JS or React — with intentional aesthetic direction, not generic AI output.