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/murphytrueman/design-system-ops/triagenpx skills add murphytrueman/design-system-ops --skill triagegit clone --depth 1 https://github.com/murphytrueman/design-system-opsWrote 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/murphytrueman/design-system-ops/triage)<a href="https://agentmods.dev/skills/murphytrueman/design-system-ops/triage"><img src="https://agentmods.dev/badge/skills/murphytrueman/design-system-ops/triage.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.00076 | $0.01733 |
| Opus 5 | $0.00038 | $0.00866 |
| Sonnet 5 | $0.00015 | $0.00347 |
| Haiku 4.5 | $0.00008 | $0.00173 |
Grade A, and why
triage 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 6d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage
A skill for quickly assessing a design system's state and recommending which skills to run first, in what order, and why. Prevents the overwhelm of running all 40 skills when 3–5 would surface the critical findings.
Context
Design System Ops has 40 skills across 5 categories: audit, validate, document, govern, and communicate. Running all of them is comprehensive but overwhelming — especially for a team encountering the plugin for the first time. The triage skill reads the system's current state and produces a prioritised run plan: which skills to run first, which to skip for now, and which to return to later.
The triage skill is intentionally lightweight. It should take no more than 5 minutes of input-gathering and produce a run plan in under a minute. The value is in sequencing, not in depth — the subsequent skills provide the depth.
Boundaries
This skill produces a run plan — it does not run other skills itself. If the user wants a full automated sweep, point them to the /full-diagnostic agent instead. If the system has a single well-defined problem ("our tokens are a mess"), skip triage and go directly to the relevant skill. Triage is for when the team does not know where to start, not when they already know.
Step 1: Quick system scan
Gather the minimum information needed to assess the system's state. This is NOT a full audit — it is a triage scan.
Ask for or confirm:
- System name and approximate size (number of components)
- Primary tech stack (React, Vue, Twig, Web Components, etc.)
- Token system: does one exist? What format? (SCSS, CSS vars, DTCG, Tailwind, none)
- Documentation: is there any? Where does it live?
- Team size: how many people work on the design system?
- Maturity self-assessment: how would the team describe their system? (New, growing, established, struggling, legacy)
- Current pain: what prompted this assessment? What is the most pressing problem?
If the user provides a codebase or repo path, do a quick scan:
- Count component directories
- Check for token files (*.tokens.json, variables.scss, etc.)
- Check for documentation files (README, docs/, etc.)
- Check for consuming apps (apps/, packages/, etc.)
- Check for drift evidence (override files, fork patterns)
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.
- 6d ago First seen · 162 lines · 76 tokens per session scan A 2809fdb6640a
triage is a skill published in the GitHub repository murphytrueman/design-system-ops (175 stars, last pushed 14d ago), licensed MIT. It adds 76 tokens to every session and 1,733 once invoked, about $0.0004 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
extract-design
Extract the full design language from any website URL. Produces 8 output files including AI-optimized markdown, visual HTML preview, Tailwind config, React theme, shadcn/ui theme, Figma variables, W3C design tokens, and CSS variables. Also runs WCAG accessibility scoring. Use when user says 'extract design', 'get…
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
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…
design-engineering
Premium design engineering skill for agentic workflows — produces high-end, distinctive UI designs using DESIGN.md as the portable contract across Pencil MCP (in-IDE canvas), Figma MCP (team handoff + design tokens), and Google Stitch (vibe exploration + AI generation). Enforces anti-generic principles, WCAG 2.2 AA…
generate-figma-screen
Kod veya açıklamadan Figma'da tam ekran/sayfa oluşturur. Yayınlanmış design system bileşenlerini arayıp instance olarak yerleştirir; hardcode değer yerine DS token'larını kullanır. "Figma'da ekran oluştur", "kodu Figma'ya çevir", "landing page çiz", "ekran tasarla", "generate screen", "UI'ı Figma'ya aktar"…
sheleg-design
Use when deciding how something LOOKS or MOVES — cinematic landing pages and hero sections, particle/WebGL, scrubbed motion, drift, dashboards, admin or internal tools, mobile screens, chat or agent interfaces, tokens, palettes, typography and the Figma border. Triggers - "design a landing" / "дизайн лендинга", "build…