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/qgolem/orc/design-systemnpx skills add qGolem/orc --skill design-systemgit clone --depth 1 https://github.com/qGolem/orcWrote 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/qgolem/orc/design-system)<a href="https://agentmods.dev/skills/qgolem/orc/design-system"><img src="https://agentmods.dev/badge/skills/qgolem/orc/design-system.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 | $0.00013 | $0.00884 |
| Opus 5 | $0.00006 | $0.00442 |
| Sonnet 5 | $0.00003 | $0.00177 |
| Haiku 4.5 | $0.00001 | $0.00088 |
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 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design System
Mode Detection
Parse $ARGUMENTS:
- If first token is
new→ Scaffold Mode (remaining tokens = system name) - Otherwise → Load Mode (first token = system name or query)
Load Mode (default)
- Discover systems:
Glob("skills/design-system/systems/*/spec.md")from the repo root - Select system:
- If
$ARGUMENTSfirst token matches a discovered system name → use it; remaining tokens are the query - If no token match and exactly one system exists → default to it silently
- If no token match and multiple systems exist → list available systems via
AskUserQuestion
- If
- Load:
Read systems/<selected>/spec.md - Present: Output the spec content. If a query was provided, highlight the relevant section.
Scaffold Mode (new <name>)
- Parse system name from
$ARGUMENTS(e.g.,new acme-brand→ name isacme-brand) - Validate name is lowercase kebab-case; reject otherwise
- Create directory:
mkdir -p systems/<name>/ - Copy template: Read
templates/spec.md, write tosystems/<name>/spec.md - Replace placeholder: Update
[System Name]and[system name]in the copied file with the actual name - Ask user:
AskUserQuestion: "I've scaffolded `systems/<name>/spec.md` with blank sections. Would you like to fill it in interactively now, or edit the file yourself later?"- Interactive → Walk through each section (Color Palette, Typography, Borders, Layout, Cards, Components, CSS, Shadows, Breakpoints, Scrollbar, Constraints), asking the user for their values
- Later → Report the file path and stop
- Report: "Design system
<name>created. Use/orc:vibe-code <name> [component]to design with it."
Examples
Load a system
/orc:design-system orc-brand
Loads systems/orc-brand/spec.md into context — full color palette, typography, layout, component patterns.
What ships with it
2 files 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.
- 3d ago First seen · 94 lines · 13 tokens per session scan A 77c0dd5f1b94
design-system is a skill published in the GitHub repository qGolem/orc (5 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 884 once invoked, about $0.0001 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-31.
Other skills, from other repositories
fidelity-gate
Build a UI against a frozen visual reference without drift - an inventory extracted before any code, a relics list, and a gate that MEASURES computed styles on a fixture carrying the reference's own data. Use when a mockup, design spec or screenshot is the contract.
roast-my-design-system
Roast the current repo's design system with real data. Runs a deterministic scanner (no tokens, 1s) that counts everything that betrays a design system, from colours and their near-identical twins to greys, spacing values, typefaces, duplicated and never-imported components, inline styles, !important and arbitrary…
a11y-audit
Dedicated WCAG 2.2 AA/AAA accessibility audit across 10 dimensions (A1-A10) covering semantic HTML, keyboard navigation, ARIA patterns, color contrast, forms, images/media, responsive/zoom, motion/animation, reading/content, and legal compliance. Goes far beyond surface-level design-review checks with deep…
design-review
UI/UX design consistency audit. Code-based DX1-DX20 checklist covering states, consistency, accessibility, responsive behavior, and interaction patterns. Optional visual audit via chrome-devtools screenshots and automated WCAG accessibility via axe-core. DAP1-DAP12 anti-pattern detection. Modes: [path], visual…
design
Intent-first UI design with conscious, traceable design decisions. Persists decisions in .interface-design/ for cross-session consistency. Includes domain exploration, design system generation (system.md + system.json), per-component construction with mandatory checkpoints, and craft validation tests. Modes: init…
cognitive-interface-audit
Comprehensive cognitive interface audit with two modes and a single tier. Planning mode designs task models, user expertise mapping, and error tolerance strategy. Audit mode evaluates mental model alignment (Norman's Gulfs), consistency (Gestalt), error tolerance (Wood 7-layer defense), cognitive load (NASA-TLX…