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 saemihemma/lead-producer-oss --skill workflow-shadcn-uigit clone --depth 1 https://github.com/saemihemma/lead-producer-ossWrote 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/saemihemma/lead-producer-oss/workflow-shadcn-ui)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/workflow-shadcn-ui"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/workflow-shadcn-ui/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/saemihemma/lead-producer-oss/workflow-shadcn-ui"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/workflow-shadcn-ui.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.00035 | $0.00570 |
| Opus 5 | $0.00017 | $0.00285 |
| Sonnet 5 | $0.00007 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
workflow-shadcn-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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
shadcn/ui Workflow
Purpose
Narrow method for shadcn/ui work: current docs, component composition, theming discipline, accessibility.
Use When
- Task explicitly mentions shadcn/ui
- React/Tailwind screen should be built from shadcn primitives
- Question is which components, how to compose, how to theme
- Brand fidelity matters for design system consistency
Do NOT Use When
- Generic frontend work with no shadcn dependency
- Full architecture design
- Pure visual brand direction (use
team-brand-team) - Broader implementation review (use
role-frontend-engineer)
Current Docs Rule
Treat shadcn/ui details as fast-moving. Use official docs whenever:
- Component APIs may have changed
- Installation/setup steps matter
- Theming or composition behavior is version-sensitive
Do not freeze volatile library details into long local prose.
Workflow
- Confirm screen or component goal.
- Choose smallest set of shadcn primitives that fit.
- Check current docs before assuming API or setup details.
- For interactive states, responsive behavior, accessibility, or browser-specific issues, validate in a real browser with Playwright or an equivalent tool.
- Review accessibility, theming, composition quality.
- Hand to Frontend Team when task goes beyond narrow method guidance.
Default Output
SHADCN/UI PLAN
==============
Goal: screen or component intent
Component Shape: chosen primitives, why they fit
Docs to Check: current APIs/setup to verify
Quality Checks: accessibility, theming consistency, responsive behavior
Pairings: frontend owner, brand owner if needed
Anti-Patterns
- Treating shadcn/ui as a full design system by itself.
- Adding custom wrappers before base primitives prove insufficient.
- Copying stale library rules instead of checking current docs.
Output Discipline
- Follow the Default Output structure as both minimum and maximum. Do not add extra sections.
- Keep findings concise: 2-5 points per section.
Anti-Drift Rules
- Do not treat shadcn/ui as a full design system. It is a component library.
- Check current docs before assuming API details. Do not freeze stale library info.
- Do not add custom wrappers before base primitives prove insufficient.
- This workflow handles shadcn/ui method, not broader frontend architecture.
- If task exceeds narrow shadcn/ui method, escalate back to LP for Frontend Team routing.
- Do not treat static code review as enough evidence when browser behavior is the question.
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 · 65 lines · 35 tokens per session scan A 50b4f6a9d956
workflow-shadcn-ui is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 8d ago), licensed MIT. It adds 35 tokens to every session and 570 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-09-03.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
antigravity-design-expert
Core UI/UX engineering skill for building highly interactive, spatial, weightless, and glassmorphism-based web interfaces using GSAP and 3D CSS.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
liquid-metal-border
Add and tune animated liquid-metal WebGL borders with the React metal-fx package. Use when buttons, icon controls, chips, tabs, cards, or selected surfaces need a metallic active, selected, hover, focus, or premium border; when implementing the MetalFx component from metal.jakubantalik.com; or when troubleshooting its…
21st-ui
Find, install, and generate UI with 21st.dev. Use when the user asks for a UI component (pricing table, hero, navbar, dashboard, form, etc.), wants design inspiration, needs a brand logo as an SVG component, or wants to generate new UI from a prompt.