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 andrewsrigom/agent-skills --skill shadcn-overview-and-code-ownershipgit clone --depth 1 https://github.com/andrewsrigom/agent-skillsWrote 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/andrewsrigom/agent-skills/shadcn-overview-and-code-ownership)<a href="https://agentmods.dev/skills/andrewsrigom/agent-skills/shadcn-overview-and-code-ownership"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/shadcn-overview-and-code-ownership/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/andrewsrigom/agent-skills/shadcn-overview-and-code-ownership"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/shadcn-overview-and-code-ownership.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.00079 | $0.00803 |
| Opus 5 | $0.00039 | $0.00402 |
| Sonnet 5 | $0.00016 | $0.00161 |
| Haiku 4.5 | $0.00008 | $0.00080 |
Grade A, and why
shadcn-overview-and-code-ownership 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 11d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
shadcn Overview And Code Ownership
Use this skill when the task is mainly about whether and how to adopt shadcn in a codebase.
Scope
- deciding when shadcn is a good fit
- the code-ownership model behind shadcn
- default adoption strategy for app teams
- routing to registry, theming, composition, and forms follow-up skills
Routing cues
- choose shadcn, adopt shadcn in an app, understand how shadcn differs from packaged component libraries, or decide the overall approach -> use this skill
components.json, CLI init,shadcn add, registries, or update workflows -> useshadcn-cli-registry-and-components-json- theme tokens, CSS variables, OKLCH colors, dark mode, or design-system defaults -> use
shadcn-theming-tokens-and-dark-mode asChild, trigger composition, dialog and dropdown interactions, local component ownership, or wrapper boundaries -> useshadcn-composition-and-trigger-patterns- form fields,
react-hook-form, validation, or form UI ownership -> useshadcn-forms-and-field-primitives
Default path
- Use shadcn when the team wants ownable UI source code instead of a sealed package abstraction.
- Start with the official CLI and add only the components the app actually needs.
- Treat generated component files as application code you are expected to edit.
- Keep local customization close to the component instead of wrapping everything immediately.
- Build a thin app-specific UI layer only after repeated patterns are clear.
When to deviate
- Pick a packaged library instead when the team does not want to own component code.
- Skip shadcn if the project already has a stable in-house design system with different primitives and conventions.
- Introduce shared wrappers only after the repetition is real and the ownership boundary is obvious.
Guardrails
- Treat shadcn components as copied source, not as a magical dependency you should never touch.
- Keep the app's design tokens and visual defaults coherent before mass-adding components.
- Prefer a small local surface over a broad imported catalog.
- Route to sibling skills once the job becomes mostly about theming, registries, composition, or forms.
What ships with it
1 file 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.
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.
- 11d ago First seen · 75 lines · 79 tokens per session scan A d30c5d42f611
shadcn-overview-and-code-ownership is a skill published in the GitHub repository andrewsrigom/agent-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 79 tokens to every session and 803 once invoked, about $0.0004 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
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…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…