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 Cratis/AI --skill cratis-components-stylinggit clone --depth 1 https://github.com/Cratis/AIWrote 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/cratis/ai/cratis-components-styling)<a href="https://agentmods.dev/skills/cratis/ai/cratis-components-styling"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-components-styling.svg" alt="Measured on agentmods" 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.00122 | $0.02759 |
| Opus 5 | $0.00061 | $0.01380 |
| Sonnet 5 | $0.00024 | $0.00552 |
| Haiku 4.5 | $0.00012 | $0.00276 |
Grade A, and why
cratis-components-styling 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 today.
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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Styling Cratis Components
Cratis Components builds on PrimeReact 11, which is unstyled-first: it ships no CSS and renders no class names of its own. Everything a Cratis application looks like comes from the layers below. Getting the setup wrong shows up as components rendering completely unstyled, which is the single most common first-run problem.
Verified product sources
| Package | Version | Verified from |
|---|---|---|
@cratis/components |
3.0.0 |
its package manifest, Styled/, and the CSS sources |
primereact |
^11.0.0 |
peer of @cratis/[email protected] |
@primereact/core, @primereact/headless, @primereact/hooks |
^11.0.0 |
peers of @cratis/[email protected] |
@primereact/styles, @primereact/types, @primeuix/themes |
optional peers | @primereact/styles/types ^11.0.0, @primeuix/themes ^3.0.0 |
primeicons |
^8.0.0 |
peer of @cratis/[email protected] |
PrimeReact is a peer dependency — install it in the application yourself.
Two copies mean two provider contexts, which breaks overlays and pass-through
silently. Remove any resolutions or overrides pin that used to work around
this.
Step 1 — What an app must do
Two things, or the components render unstyled:
-
Mount
CratisComponentsProvider(from@cratis/components/Common) above every Cratis component. It wraps the PrimeReact provider and merges your configuration over the Cratis defaults, so anything you pass wins. -
Import the stylesheets explicitly, in this order — components no longer import their own CSS:
import '@cratis/components/tokens'; // the --cratis-* layer every component reads import '@cratis/components/styles'; // every component stylesheet, in one file import '@cratis/components/theme'; // optional: the license-free baseline look
Order matters: both styles and theme consume the tokens. The styles entry
also vendors the split-pane CSS the DataPage details pane needs, so importing
it is not optional even in a fully custom-styled app.
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.
- today First seen · 222 lines · 122 tokens per session scan A 85cbd62b09e5
cratis-components-styling is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed today), licensed MIT. It adds 122 tokens to every session and 2,759 once invoked, about $0.0006 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-06.
Other skills, from other repositories
polish-ui
Design-quality workflow that combines design taste, aesthetic direction, image-to-code, a Web Interface Guidelines audit, and real-browser verification. Use when building or polishing a UI surface, implementing a mockup/screenshot, or when asked to make a page "look great".
review-design
Reviews frontend components for design quality and UI/UX standards. Use when checking component styling, responsiveness, accessibility, or when asked to review a design.
ui-accessibility
Review interface work for accessible interaction, semantics, and resilient responsive behavior.
ui-styling
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns…
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications, OR when they provide screenshots/images/designs to replicate or draw inspiration from. For screenshot inputs, extracts design guidelines first using…
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.