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 furkangonel/cowrangler --skill design-systemgit clone --depth 1 https://github.com/furkangonel/cowranglerWrote 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/furkangonel/cowrangler/design-system)<a href="https://agentmods.dev/skills/furkangonel/cowrangler/design-system"><img src="https://agentmods.dev/badge/skills/furkangonel/cowrangler/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/furkangonel/cowrangler/design-system"><img src="https://agentmods.dev/badge/skills/furkangonel/cowrangler/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.00016 | $0.02537 |
| Opus 5.5 | $0.00006 | $0.01015 |
| Sonnet 5.5 | $0.00003 | $0.00507 |
| Haiku 4.5 | $0.00002 | $0.00254 |
Grade A, and why
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 — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design System SOP
When to Use
- User wants to create or document a design system, component library, or style guide
- User asks about design tokens, typography scales, color palettes, or spacing
- User is building a UI kit or documenting component APIs
- User wants to ensure visual consistency across a product
Part 1 — Design Tokens
Tokens are the single source of truth for all visual decisions. Document them in three tiers:
Tier 1: Primitive Tokens (raw values)
{
"color": {
"blue-50": "#eff6ff",
"blue-100": "#dbeafe",
"blue-500": "#3b82f6",
"blue-700": "#1d4ed8",
"blue-900": "#1e3a8a",
"gray-50": "#f9fafb",
"gray-100": "#f3f4f6",
"gray-500": "#6b7280",
"gray-900": "#111827",
"white": "#ffffff",
"black": "#000000"
},
"spacing": {
"0": "0px",
"1": "4px",
"2": "8px",
"3": "12px",
"4": "16px",
"6": "24px",
"8": "32px",
"12": "48px",
"16": "64px"
},
"radius": {
"none": "0px",
"sm": "4px",
"md": "8px",
"lg": "12px",
"xl": "16px",
"full": "9999px"
},
"shadow": {
"sm": "0 1px 2px rgba(0,0,0,0.05)",
"md": "0 4px 6px rgba(0,0,0,0.07)",
"lg": "0 10px 15px rgba(0,0,0,0.1)",
"xl": "0 20px 25px rgba(0,0,0,0.1)"
}
}
Tier 2: Semantic Tokens (intent-named aliases)
{
"color": {
"brand-primary": "{color.blue-500}",
"brand-primary-hover": "{color.blue-700}",
"text-primary": "{color.gray-900}",
"text-secondary": "{color.gray-500}",
"text-inverse": "{color.white}",
"bg-surface": "{color.white}",
"bg-subtle": "{color.gray-50}",
"bg-overlay": "rgba(0,0,0,0.5)",
"border-default": "{color.gray-100}",
"border-strong": "{color.gray-500}",
"status-success": "#16a34a",
"status-warning": "#d97706",
"status-error": "#dc2626",
"status-info": "{color.blue-500}"
},
"spacing": {
"component-padding-sm": "{spacing.2}",
"component-padding-md": "{spacing.4}",
"component-padding-lg": "{spacing.6}",
"layout-section-gap": "{spacing.12}"
}
}
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 · 296 lines · 16 tokens per session scan A 896cc5863bc6
design-system is a skill published in the GitHub repository furkangonel/cowrangler (1 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 2,537 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
design-md
Author/validate/export Google's DESIGN.md token spec files.
design-system-creator
Builds comprehensive design systems and design bibles with production-ready CSS. Expert in design tokens, component libraries, CSS architecture. Use for design system creation, token architecture, component documentation, style guide generation. Activate on "design system", "design tokens", "CSS architecture"…
hs-frontend-development
Design and build production-grade frontend interfaces, context first - capture PRODUCT.md (strategy) and DESIGN.md (visual system), pull reusable tokens into a design system, and apply shared UX/UI rules (color, typography, layout, motion, accessibility, anti-patterns) for brand and product surfaces. Its capabilities…
design-system-starter
Use this skill when creating or evolving design systems for applications. Provides design token structures, component architecture patterns, documentation templates, and accessibility guidelines. Ensures consistent, scalable, and accessible UI design across products.
figma-bridge
Extract design information from Figma files. Pull design tokens, component structure, colors, typography, spacing, and export assets. Use when the user asks about their Figma designs, needs to extract design tokens, or wants to convert Figma designs to code. Triggers on: "figma", "design tokens", "get colors from…
vibe-coding-advisor
Inject UX principle context into your AI coding session before generating components. Maps component types (forms, tables, dashboards, navigation, checkout, etc.) to relevant UX principles, fetches their vibeCodingPrompts, and returns an assembled context block ready to paste into Cursor, Claude Code, Windsurf, or any…