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/policyengine/policyengine-claude/policyengine-designnpx skills add PolicyEngine/policyengine-claude --skill policyengine-designgit clone --depth 1 https://github.com/PolicyEngine/policyengine-claudeWhat 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.00161 | $0.03080 |
| Opus 5 | $0.00081 | $0.01540 |
| Sonnet 5 | $0.00032 | $0.00616 |
| Haiku 4.5 | $0.00016 | $0.00308 |
Grade A, and why
policyengine-design 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PolicyEngine design system
Design tokens live as CSS custom properties in @policyengine/ui-kit/theme.css. Every
frontend imports that one file. The canonical version is @policyengine/ui-kit ^0.4.0 —
the version app-v2 pins. Ignore claims tied to 0.5/0.6/0.9; treat 0.4.0 as ground truth and
re-check node_modules/@policyengine/ui-kit when precision matters.
Setup: the two imports
/* globals.css — order matters; Tailwind must come first */
@import "tailwindcss";
@import "@policyengine/ui-kit/theme.css";
Next.js needs postcss.config.mjs = { plugins: { "@tailwindcss/postcss": {} } } (install
@tailwindcss/postcss + postcss). A Vite app uses the @tailwindcss/vite plugin instead —
no PostCSS config. Do not add postcss-import or autoprefixer (@tailwindcss/postcss
handles both), and do not add a second @import "tailwindcss" (theme.css does not import
it). If the consumer's own utility classes go missing in a monorepo, scope source detection:
@import "tailwindcss" source("./src");.
The three-layer theme.css
theme.css (source: ui-kit src/theme/tokens.css, vendored from design-system v0.3.0) has
three layers:
Layer 1 :root { --primary: #2C7A7B; --chart-1: #319795; ... } raw shadcn/ui semantic values
Layer 2 @theme inline { --color-primary: var(--primary); } bridge :root → Tailwind utilities
Layer 3 @theme { --color-teal-500: #319795; --text-sm: 14px; } brand palette, fonts, sizes, spacing
@theme vs @theme inline — the mechanism
@theme inlinekeeps thevar()reference, so the utility resolves it at runtime. Use it whenever a token points at a:rootvariable — that is what letsbg-primaryfollow a.darkoverride. All shadcn/ui semantic tokens use@theme inline.@themebakes a literal value into the generated CSS at build time. Use it for the fixed brand palette (teal-500is always#319795), font sizes, spacing, breakpoints.
Getting these backwards is the classic bug: @theme { --color-primary: var(--primary); } bakes
the literal string var(--primary) and never re-resolves.
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 · 187 lines · 161 tokens per session scan A 6720c9b59c88
policyengine-design is a skill published in the GitHub repository PolicyEngine/policyengine-claude (31 stars, last pushed 8d ago), licensed MIT. It adds 161 tokens to every session and 3,080 once invoked, about $0.0008 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
design-guide
Paperclip UI design system guide for building consistent, reusable frontend components. Use when creating new UI components, modifying existing ones, adding pages or features to the frontend, styling UI elements, or when you need to understand the design language and conventions. Covers: component creation, design…
Shade ShadCN install
Guardrails for running pnpm dlx shadcn@latest add in Shade — never overwrite existing components, fresh branch first, swap raw colours for semantic tokens after integrating. Trigger when the user proposes a shadcn add, or when a fresh ShadCN-shaped file lands in apps/shade/src/components/ui.
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…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
author-component
Create or review Blazor components (.razor files) with correct architecture. USE FOR: writing new Blazor components that do NOT involve JavaScript interop, implementing parameters and EventCallback, RenderFragment slots, component lifecycle (OnInitializedAsync, OnParametersSet), async patterns, IAsyncDisposable…
obsidian-layout-adjustment
Workflow for working with the user on changing how Obsidian looks using CSS snippets. Use this whenever the user asks to restyle Obsidian, tune a vault's visual layout, adjust tabs, sidebars, note surfaces, properties, backlinks, graph panes, file explorer rows, icons, links, shadows, active states, or CSS snippets.…