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 xiaojiou176-open/shadcn-brief --skill openui-workspace-deliverygit clone --depth 1 https://github.com/xiaojiou176-open/shadcn-briefWrote 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/xiaojiou176-open/shadcn-brief/openui-workspace-delivery)<a href="https://agentmods.dev/skills/xiaojiou176-open/shadcn-brief/openui-workspace-delivery"><img src="https://agentmods.dev/badge/skills/xiaojiou176-open/shadcn-brief/openui-workspace-delivery/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/xiaojiou176-open/shadcn-brief/openui-workspace-delivery"><img src="https://agentmods.dev/badge/skills/xiaojiou176-open/shadcn-brief/openui-workspace-delivery.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.00045 | $0.00671 |
| Opus 5 | $0.00023 | $0.00336 |
| Sonnet 5 | $0.00009 | $0.00134 |
| Haiku 4.5 | $0.00005 | $0.00067 |
Grade A, and why
shadcn-brief-workspace-delivery 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 12d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ShadcnBrief Workspace Delivery
Teach the agent how to install, connect, and use ShadcnBrief as a local MCP-first UI generation and review workspace.
Use this skill when
- the user wants to generate or review shadcn-style UI from a local MCP server
- the host can run a local
stdioMCP server - the user wants one inspectable proof loop before any public claim
What this packet teaches
- how to wire the local ShadcnBrief MCP server into OpenHands or OpenClaw
- which ShadcnBrief MCP tools are safe and useful first
- how to move from installation to a first proof loop
- how to keep claims grounded in local MCP and repo-owned proof instead of marketplace hype
Start here
- Read references/INSTALL.md
- Load the right host config from:
- Skim the tool surface in references/CAPABILITIES.md
- Run the proof loop in references/DEMO.md
- If attach or proof fails, use references/TROUBLESHOOTING.md
Recommended workflow
shadcn_brief_scan_workspace_profileshadcn_brief_plan_changeshadcn_brief_generate_uishadcn_brief_quality_gateshadcn_brief_build_review_bundle
Suggested first prompt
Use ShadcnBrief to inspect this workspace and prepare one safe-first UI
delivery step. Start with shadcn_brief_scan_workspace_profile and
shadcn_brief_plan_change. If the workspace looks healthy, run shadcn_brief_generate_ui
for one small component or page change, then run shadcn_brief_quality_gate and
summarize what a reviewer should inspect next.
Success checks
- the host can launch the ShadcnBrief MCP server from the provided config
- the workspace scan returns a real profile instead of placeholder text
- the plan/generate flow yields a concrete UI output or change plan
- the proof loop stays inside local MCP and repo-owned evidence
What ships with it
15 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.
- .claude-plugin/plugin.json 276 B
- .mcp.json 254 B
- commands/openui-install.md 676 B
- commands/openui-proof.md 362 B
- manifest.yaml 1.5 KB
- README.md 1.2 KB
- references/CAPABILITIES.md 1.0 KB
- references/DEMO.md 946 B
- references/INSTALL.md 945 B
- references/OPENCLAW_MCP_CONFIG.json 302 B
- references/OPENHANDS_MCP_CONFIG.json 268 B
- references/README.md 481 B
- references/TROUBLESHOOTING.md 754 B
- samples/claude-code.mcp.json 364 B
- skills/openui-local-install/SKILL.md 1.0 KB
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.
- 12d ago First seen · 72 lines · 45 tokens per session scan A 66c1f10f053b
shadcn-brief-workspace-delivery is a skill published in the GitHub repository xiaojiou176-open/shadcn-brief (1 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 671 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-31.
Other skills, from other repositories
visual-qa-verification
Automated visual QA with pixel-level diff comparison, iterative fix loop, and cross-browser verification. Uses pixelmatch for programmatic screenshot comparison with region-based analysis. Covers responsive checks, Lighthouse audits, and accessibility validation. Keywords: verify app, visual QA, compare to Figma…
canva-token-inference
AI-powered design token extraction from Canva screenshots. Uses Claude vision to infer colors, typography, spacing, and effects with confidence scoring. Presents tokens for user confirmation before locking. Keywords: Canva tokens, token inference, design tokens, Canva extraction, AI token detection, color extraction…
design-token-lock
Extracts exact design values from Figma and writes a lockfile that becomes the single source of truth for colors, typography, spacing, and text content. Generates tailwind.config.ts and tokens.css from the lockfile. Keywords: design tokens, lockfile, Figma variables, token extraction, style drift, Tailwind config…
export-design-system
Exports generated components + design-tokens.lock.json as a publishable pnpm workspace. Generates a framework-agnostic tokens package and a framework-specific component library (React/Vue/Svelte via Vite library mode, React Native via tsc). Includes Tailwind preset, ThemeProvider, Changesets versioning, and a properly…
figma-intake
Structured interview that auto-discovers Figma file structure, project context, and asks 3-5 targeted questions to produce a build-spec.json. Entry point for the autonomous build pipeline. Keywords: Figma intake, build spec, project discovery, figma interview, build plan.
indesign-conversion
Convert an exported Adobe InDesign IDML package or PDF into typed React components, design tokens, and Storybook stories via the @aurelius/pipeline InDesign pipeline. Use when a designer hands you an .idml or .pdf and you need a starting React component set. Keywords: InDesign to React, IDML, PDF to React, indesign…