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 perniemann/pnCore --skill pn-design-systemgit clone --depth 1 https://github.com/perniemann/pnCoreWrote 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/perniemann/pncore/pn-design-system)<a href="https://agentmods.dev/skills/perniemann/pncore/pn-design-system"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-design-system/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/perniemann/pncore/pn-design-system"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-design-system.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.00054 | $0.01096 |
| Opus 5.5 | $0.00022 | $0.00438 |
| Sonnet 5.5 | $0.00011 | $0.00219 |
| Haiku 4.5 | $0.00005 | $0.00110 |
Grade A, and why
pn-design-system 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 1mo 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design system skill
When to use
- Defining or refactoring design tokens
- Setting up CSS variable architecture
- Creating or enforcing spacing and typography scales
- Implementing light/dark or multi-theme support
- Auditing components for consistency
- Preventing one-off colors, spacing, or font sizes
Token hierarchy
- Primitive tokens: Raw values (e.g.
--color-blue-500: #3b82f6,--space-4: 1rem,--font-sans: 'Inter', sans-serif). No semantic meaning. - Semantic tokens: Map primitives to intent (e.g.
--color-primary: var(--color-blue-500),--spacing-md: var(--space-4),--font-body: var(--font-sans)). - Component tokens: Component-specific overrides (e.g.
--button-bg: var(--color-primary),--card-padding: var(--spacing-lg)). Prefer semantic over primitive in components.
CSS variable naming conventions
- Prefix by category:
--color-,--space-,--font-,--radius-,--shadow-,--duration-,--ease-. - Scale suffixes: Use numeric or semantic scale (e.g.
--space-1through--space-12, or--space-xs,--space-sm,--space-md,--space-lg,--space-xl). - Semantic names: Prefer
--color-text-primaryover--color-gray-900in component usage; reserve primitives for token definitions. - No one-offs: Avoid inline values like
color: #3b82f6ormargin: 13px; use tokens.
Spacing scale
- Define a consistent scale (e.g. 4px base: 4, 8, 12, 16, 24, 32, 48, 64, 96).
- Map to tokens:
--space-1,--space-2, etc. - Use for margin, padding, gap. Avoid arbitrary values.
Typography scale
- Define type scale (e.g. 12, 14, 16, 18, 24, 30, 36, 48).
- Map to tokens:
--text-xs,--text-sm,--text-base,--text-lg,--text-xl, etc. - Include line-height and letter-spacing where needed.
- Use
clamp()or fluid typography for responsive scaling when appropriate.
Base styles: prefers-reduced-motion (required)
When defining global/base CSS (e.g. globals.css, base.css), always add:
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.
- 1mo ago First seen · 84 lines · 54 tokens per session scan A c3b2ffac6ad8
pn-design-system is a skill published in the GitHub repository perniemann/pnCore (0 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 1,096 once invoked, about $0.0002 per session on Opus 5.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-03.
Other skills, from other repositories
design-context-extract
Extract design DNA from app screenshots, live URLs, or screen recordings using Google Stitch — color palettes, typography, spacing tokens, component patterns, and motion specs as design-tokens.json or Tailwind config. Use when the user points to a screenshot, URL, or video and asks to extract or audit the design…
figma-design-handoff
Figma-to-code design handoff patterns including Figma Variables to design tokens pipeline, component spec extraction, Dev Mode inspection, Auto Layout to CSS Flexbox/Grid mapping, and visual regression with Applitools. Use when converting Figma designs to code, documenting component specs, setting up design-dev…
animation-motion-design
Animation and motion design patterns using Motion library (formerly Framer Motion) and View Transitions API. Use when implementing component animations, page transitions, micro-interactions, gesture-driven UIs, or ensuring motion accessibility with prefers-reduced-motion.
component-search
Search 21st.dev component registry for production-ready React components. Finds components by natural language description, filters by framework and style system, returns ranked results with install instructions. Use when looking for UI components, finding alternatives to existing components, or sourcing design system…
apply-mantel-styles
Provides guidelines for applying Mantel's brand styles to diagrams and frontend components. Use when asked to create visuals that need to align with Mantel's branding.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…