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-theming-tokens-and-dark-modegit 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-theming-tokens-and-dark-mode)<a href="https://agentmods.dev/skills/andrewsrigom/agent-skills/shadcn-theming-tokens-and-dark-mode"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/shadcn-theming-tokens-and-dark-mode/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-theming-tokens-and-dark-mode"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/shadcn-theming-tokens-and-dark-mode.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.00065 | $0.00669 |
| Opus 5 | $0.00032 | $0.00334 |
| Sonnet 5 | $0.00013 | $0.00134 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
shadcn-theming-tokens-and-dark-mode 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
shadcn Theming Tokens And Dark Mode
Use this skill when the task is mainly about visual defaults, token strategy, or dark-mode behavior in a shadcn app.
Scope
- theme tokens
- CSS variables mode
- semantic color mapping
- dark mode strategy
- keeping component-level styling overrides under control
Routing cues
- shadcn theming,
:root, CSS variables, OKLCH colors, semantic tokens, dark mode, theme provider,next-themes, or visual consistency across components -> use this skill - if the work is mainly about CLI init or
components.json-> useshadcn-cli-registry-and-components-json - if the work is mainly about component composition and trigger behavior -> use
shadcn-composition-and-trigger-patterns
Default path
- Use CSS variables mode for app-wide theming.
- Define semantic tokens first: background, foreground, card, popover, primary, secondary, muted, accent, border, input, ring, and chart or sidebar tokens if the app needs them.
- Keep brand decisions in token values, not repeated utility overrides inside every component.
- Use one dark-mode strategy for the whole app and wire it early.
- Let components consume tokens through their default class contracts before adding custom variants.
When to deviate
- Use hardcoded per-component utility styling only when the component is intentionally one-off.
- Add extra token families only when a repeated product surface truly needs them.
- Skip dark mode only when the product has a deliberate single-theme stance.
Guardrails
- tokens should describe semantics, not page-specific hacks
- brand color changes belong in variables, not in mass component edits
- dark mode should be an application decision, not a component-by-component experiment
- keep contrast and readability intact when shifting tokens
Avoid
- styling every shadcn component with ad hoc utility overrides instead of fixing the token layer
- creating token names that encode one page or one feature
- adding several parallel dark-mode patterns in the same app
- using theme state to solve layout or composition problems
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.
- 12d ago First seen · 73 lines · 65 tokens per session scan A fb45f5e22f11
shadcn-theming-tokens-and-dark-mode is a skill published in the GitHub repository andrewsrigom/agent-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 65 tokens to every session and 669 once invoked, about $0.0003 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 $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
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.
reveal-hover-effect
Build cursor-following spotlight reveals that expose a second aligned image through a soft radial mask. Use for hover-to-color, before-and-after, x-ray, material, texture, product-detail, and illustrated hero effects where a desaturated or embossed base image should remain visible while another treatment follows an…
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.