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 skills/decocms/studio/decocms-uinpx skills add decocms/studio --skill decocms-uigit clone --depth 1 https://github.com/decocms/studioWhat 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.00091 | $0.01141 |
| Opus 5 | $0.00046 | $0.00571 |
| Sonnet 5 | $0.00018 | $0.00228 |
| Haiku 4.5 | $0.00009 | $0.00114 |
Grade A, and why
decocms-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 3d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
decocms product design system (@decocms/ui)
React 19 components built on Radix primitives, styled with Tailwind CSS v4 semantic tokens. Light and dark themes work out of the box. Browse every component and token at https://designsystem.decocms.com/
Install (new project)
bun add @decocms/ui react react-dom
Requirements: React 19 and Tailwind CSS v4 (bun add -d tailwindcss @tailwindcss/vite
plus the tailwindcss() plugin in vite.config.ts).
Make the design-system stylesheet the FIRST import of the app's CSS entry point —
it pulls in Tailwind itself, all tokens, and the bundled fonts (Inter + Commit Mono).
Do NOT also @import "tailwindcss" yourself:
@import "@decocms/ui/styles/global.css";
Tailwind only scans app source by default; if the app's classes come exclusively
from @decocms/ui components this already works — the package declares its own
@source.
Peers: install react-hook-form if you use the form component, and sonner
if you use toasts (sonner component). They are peers so the app and the design
system share one instance — never bundle a second copy.
Imports
No barrel export. Import each component from its subpath, extensionless:
import { Button } from "@decocms/ui/components/button";
import { Dialog, DialogContent, DialogTrigger } from "@decocms/ui/components/dialog";
import { cn } from "@decocms/ui/lib/utils";
import { useIsMobile } from "@decocms/ui/hooks/use-mobile";
Exception — inside the decocms/studio monorepo, workspace imports keep the
source extension: @decocms/ui/components/button.tsx.
Rules
- Semantic tokens only, never raw palette.
bg-primary,text-muted-foreground,bg-destructive,border-border— neverbg-red-500ortext-zinc-400. Available color roles:background,foreground,card,popover,primary,secondary,muted,accent,destructive,success,warning,special(AI/highlight moments),brand,border,input,ring,sidebar-*(sidebar surfaces),chart-1..5(data viz). Most roles pair with a*-foregroundtext token. - Dark mode is automatic via the
.darkclass on a root element — never hardcode colors or writedark:overrides that bypass tokens. - Compose, don't fork. Extend components with
className+cn(); add variants through the component'scvaconfig rather than wrapping with custom styles. font-boldrenders at weight 650 (custom scale); body text is 450. Radius scale derives from--radius(default 0.375rem).- User-facing copy comes from the app, passed as props — components ship only overridable English defaults.
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.
- 3d ago First seen · 101 lines · 91 tokens per session scan A 9968072c4307
decocms-ui is a skill published in the GitHub repository decocms/studio (402 stars, last pushed yesterday), licensed MIT. It adds 91 tokens to every session and 1,141 once invoked, about $0.0005 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-30.
Other skills, from other repositories
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
react-core
@copilotkit/react-core — mount the CopilotKit provider (from @copilotkit/react-core/v2) in a Next.js App Router / React Router v7 / TanStack Start / SPA app, drop in CopilotChat/CopilotPopup/CopilotSidebar (v2 chat components ship from react-core/v2 — NOT react-ui, which is CSS-only in v2), access and subscribe to…
implementing-command-palettes
Use when building Cmd+K command palettes in React - covers keyboard navigation with arrow keys, keeping selected items in view with scrollIntoView, filtering with shortcut matching, and preventing infinite re-renders from reference instability.
formkit
Use when working with FormKit forms, validation, schema, or custom inputs in React, Vue, or Nuxt projects.
novu-inbox-integration
Integrate Novu's in-app notification inbox into web applications. Supports React, Next.js, and vanilla JavaScript. Includes the Inbox component (bell icon + notification feed), composable components (Bell, Notifications, InboxContent, Preferences), headless hooks, branded theming, custom render props, multi-tenancy…
react-email
Use when creating HTML email templates with React components - welcome emails, password resets, notifications, order confirmations, newsletters, or transactional emails.