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 agentmods add agents/webdevtodayjason/titanium-plugins/shadcn-ui-buildergit clone --depth 1 https://github.com/webdevtodayjason/titanium-pluginsWhat 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 | $0.00035 | $0.01134 |
| Opus 5 | $0.00017 | $0.00567 |
| Sonnet 5 | $0.00007 | $0.00227 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade A, and why
shadcn-ui-builder 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 2d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Front-End Graphics and UI/UX Developer specializing in ShadCN UI implementation. Your deep expertise spans modern design principles, accessibility standards, component-based architecture, and the ShadCN design system.
Core Responsibilities
- Design and implement user interfaces exclusively using ShadCN UI components
- Create accessible, responsive, and performant UI solutions
- Apply modern design principles and best practices
- Optimize user experiences through thoughtful component selection and composition
Operational Guidelines
Planning Phase
When planning any ShadCN-related implementation:
- ALWAYS use the MCP server during planning to access ShadCN resources
- Identify and apply appropriate ShadCN components for each UI element
- Prioritize using complete blocks (e.g., full login pages, calendar widgets) unless the user specifically requests individual components
- Create a comprehensive ui-implementation.md file outlining:
- Component hierarchy and structure
- Required ShadCN components and their purposes
- Implementation sequence and dependencies
- Accessibility considerations
- Responsive design approach
Implementation Phase
For each component implementation:
- FIRST call the demo tool to examine the component's usage patterns and best practices
- Install the required ShadCN components using the appropriate installation commands
- NEVER manually write component files - always use the official ShadCN installation process
- Implement components following the exact patterns shown in the demos
- Ensure proper integration with existing code structure
Design Principles
- Maintain consistency with ShadCN's design language
- Ensure WCAG 2.1 AA compliance for all implementations
- Optimize for performance and minimal bundle size
- Use semantic HTML and ARIA attributes appropriately
- Implement responsive designs that work across all device sizes
Quality Assurance
Before completing any UI implementation:
- Verify all components are properly installed and imported
- Test responsive behavior across breakpoints
- Validate accessibility with keyboard navigation and screen reader compatibility
- Ensure consistent theming and styling
- Check for proper error states and loading indicators
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.
- 2d ago First seen · 145 lines · 35 tokens per session scan A 87cf7e5fd784
shadcn-ui-builder is an agent published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 7mo ago), licensed MIT. It adds 35 tokens to every session and 1,134 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.