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.
git 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/commands/xiaojiou176-open/shadcn-brief/openui-install)<a href="https://agentmods.dev/commands/xiaojiou176-open/shadcn-brief/openui-install"><img src="https://agentmods.dev/badge/commands/xiaojiou176-open/shadcn-brief/openui-install/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/commands/xiaojiou176-open/shadcn-brief/openui-install"><img src="https://agentmods.dev/badge/commands/xiaojiou176-open/shadcn-brief/openui-install.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.00000 | $0.00170 |
| Opus 5 | $0.00000 | $0.00085 |
| Sonnet 5 | $0.00000 | $0.00034 |
| Haiku 4.5 | $0.00000 | $0.00017 |
Grade A, and why
openui-install 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 10d 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
ShadcnBrief install
Use this bundle when you want the shortest honest path to add ShadcnBrief to a local Claude Code or OpenClaw workflow.
- Build the repo if the runtime path is missing.
npm installnpm run build
- Open the repo-owned starter bundles.
packages/skills-kit/starter-bundles/claude-code.mcp.jsonpackages/skills-kit/starter-bundles/openclaw.mcp.json
- Copy the starter JSON into your local host config and replace
/ABS/PATH/ShadcnBriefwith the real checkout path. - Keep the truth boundary visible.
- This bundle helps with install and proof.
- It does not prove an official marketplace listing or hosted runtime.
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.
- 10d ago First seen · 17 lines · 0 tokens per session scan A a49616419cb0
openui-install is a command published in the GitHub repository xiaojiou176-open/shadcn-brief (1 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 170 tokens. 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 commands, from other repositories
build-from-canva
You are the master orchestrator for converting a Canva design into a fully working, tested React application. You receive a Canva URL and guide the entire process through 12 phases, using specialized skills and agents.
build-from-figma
You are the master orchestrator for converting a Figma design into a fully working, tested React application. You receive a Figma URL and guide the entire process through 9 phases, using specialized skills and agents.
build-from-screenshot
You are the master orchestrator for converting screenshots or a live URL into a fully working, tested application. You receive one or more image file paths OR a URL and guide the entire process through 12 phases, using specialized skills and agents. The output target (React, Vue, Svelte, React Native) is determined…
build-from-conversation
You are the master orchestrator for building a working, tested app from nothing but a conversation. The user describes what they want; you interview them, generate a real Figma design from the resulting brief, and then hand off to the existing /build-from-figma pipeline, which runs unchanged from there. "Talk to…
export-design-system
Export the generated components and design tokens from this project as a publishable pnpm workspace with a framework-agnostic token package and a framework-specific component library (Vite library mode for web, tsc for React Native).
ci
Runs the same checks as /verify-all but in non-interactive, machine-readable mode. Designed for CI pipelines, pre-merge gates, and automation: no prompts, JSON output, exit code reflects overall pass/fail.