Borrowing it
Nothing to install: this file belongs to zhu-kai/whodecided. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zhu-kai/whodecided/main/.claude/skills/workbench-ui/SKILL.mdgit clone --depth 1 https://github.com/zhu-kai/whodecidedWrote 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/zhu-kai/whodecided/workbench-ui)<a href="https://agentmods.dev/skills/zhu-kai/whodecided/workbench-ui"><img src="https://agentmods.dev/badge/skills/zhu-kai/whodecided/workbench-ui.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.1 | $0.00040 | $0.00364 |
| Opus 5 | $0.00020 | $0.00182 |
| Sonnet 5 | $0.00008 | $0.00073 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
workbench-ui 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 8d 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.
What it actually says
The workbench is ONE template-literal string emitting a self-contained page (embedded JSON, vanilla JS, no CDN).
Escaping trap (breaks the page silently): inside the emitted <script>, every backslash needs doubling for the outer literal - \\n not \n, \\" not \", and regex character classes like /[/]/ instead of escaped slashes. A single unescaped backslash produces a blank page with a console error.
Conventions:
- All user-visible strings live in the
Tobject, English only. - One signal, one cue: risk is the red left edge (high only), category is the small colored label, relationships are chips under the text. Never stack a second cue for the same fact.
- Negative/actionable info goes in the drawer's needs-attention block; healthy states fold into collapsed
<details class="dsec">sections. - Benign categories render muted; only silent (red) should pull the eye.
Verify (required before done):
npm run build && npm test.- Render real data - a repo with a populated
.wdd/(not synthetic fixtures), viawdd review --htmlor a small node script importingdist/render/html.js. - Serve over http (file:// is blocked for MCP browsers), open with Playwright: assert zero console errors, click through a decision drawer, screenshot and actually look at it.
- Clean up: temp server, screenshots, scratch scripts.
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.
- 8d ago First seen · 21 lines · 40 tokens per session scan A 2b034096e1f1
workbench-ui is a skill published in the GitHub repository zhu-kai/whodecided (22 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 364 once invoked, about $0.0002 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
frontend-design
Production-grade UI/UX guidance — not generic AI slop. Triggers on design, UI, frontend, component, styling, layout, make it look good.
browser-extension-developer
Use this skill when developing or maintaining browser extension code in the browser/ directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
code-review
Review frontend code for best practices, bugs, and improvements. Use when reviewing PRs, checking code quality, or before committing.
optimise-seo
Implements Next.js crawlability, metadata, canonicals, status codes, JSON-LD, hreflang, and crawler policy with served-page evidence. Use when asked to "fix SEO", "add a sitemap", "fix soft 404s", or "add llms.txt". For demand research, briefs, or Search Console monitoring use seo-program.
ui-design
Designs and builds React/Next/Tailwind UI and audits visual and interaction defects. Use when asked to "build a landing page", "extract our design system", "add dark mode", "make this responsive", "remove UI slop", or "audit this component". For product decisions use product-design; for browser measurements use…
typography-audit
Audits font loading, type scales, measure, spacing, OpenType, and rendered punctuation with 78 scoped rules. Use when asked to "audit typography", "fix the fonts", or "review my type system". For a new visual direction use ui-design Direction; for general UI defects use ui-design Audit.