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 cuesoftinc/oss-engineering-standards --skill cuelabs-design-standardgit clone --depth 1 https://github.com/cuesoftinc/oss-engineering-standardsWrote 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/cuesoftinc/oss-engineering-standards/cuelabs-design-standard)<a href="https://agentmods.dev/skills/cuesoftinc/oss-engineering-standards/cuelabs-design-standard"><img src="https://agentmods.dev/badge/skills/cuesoftinc/oss-engineering-standards/cuelabs-design-standard/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/cuesoftinc/oss-engineering-standards/cuelabs-design-standard"><img src="https://agentmods.dev/badge/skills/cuesoftinc/oss-engineering-standards/cuelabs-design-standard.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.00058 | $0.00593 |
| Opus 5.5 | $0.00023 | $0.00237 |
| Sonnet 5.5 | $0.00012 | $0.00119 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
cuelabs-design-standard 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 25d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CueLABS Design Standard
This standard covers CueLABS product design systems. The Cuesoft Design System
Figma file and the @cuesoftinc/design-system package belong to
cuesoft-design-standard, not here.
Maintain design artifacts as implementation contracts. Preserve each product's visual identity while keeping shared foundations, naming, accessibility, and QA methods consistent.
Read the relevant references
- Read references/figma-and-design.md for design documentation, variables, components, states, prototype wiring, content integrity, and Figma-specific constraints.
- Use the "Design QA loop" rule in
figma-and-design.mdwhen planning or closing audit/fix/re-verify rounds. For multi-agent orchestration and merge gates, activate$cuelabs-engineering-standardswhen installed.
Workflow
- Inspect product decisions, design documentation, current code, and the actual design file before changing either side.
- Determine whether the task affects foundations, components, screens, content, flows, accessibility, motion, or parity.
- Keep product tokens in true light/dark modes and pair accent fills with explicit on-accent text tokens.
- Build screens from live component instances and include required default, empty, loading, error, and destructive states where the product contract calls for them.
- Keep implementation notes in component descriptions or documentation, not visible product canvases.
- Wire and verify named prototype flows. Prove core-flow reachability and eliminate unintended dead ends.
- Run independent completeness, content, accessibility, and polish passes. Record findings with stable node or file identifiers and severity.
- Verify each fix against the artifact and update the implementation contract when a design decision changes.
Guardrails
- Do not fabricate customer claims, usage numbers, pricing, research results, or third-party endorsements.
- Do not ship a screen that lacks its required states.
- Do not represent dark mode as component variants when token modes are the governing mechanism.
- Do not treat screenshots as a substitute for inspectable tokens and components.
- Do not mark a QA finding resolved based only on the builder's statement.
- Do not force a shared visual style where the standard requires only shared structure or behavior.
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.
- 25d ago Changed · +4 lines 06da947a9589
- 1mo ago Changed · +1 lines 5fbb249979dc
- 1mo ago First seen · 58 lines · 58 tokens per session scan A 1bf4195348a7
cuelabs-design-standard is a skill published in the GitHub repository cuesoftinc/oss-engineering-standards (5 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 593 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-08-31.
Other skills, from other repositories
openclaw-carapace
Build or modify OpenClaw application UI using canonical semantic tokens, themes, shared CSS foundations, consumer adapters, and established local primitives. Use for product interfaces, component styling, theme work, or design-token integration.
ui-designer/html-prototype
An interactive HTML prototype is a browser-openable web page that shows design options and lets people click to choose one.
frontend-design
A front-end coding tool for building distinctive web pages and interface components. It focuses on unusual layouts, visual styling, animations, and production-ready code rather than generic-looking screens.
variant-design-system
For product-critical work, also read references/workflow/design-declaration.md and references/workflow/product-integrity-gate.md. A confirmed design system locks the declaration's product constraints as well as visual tokens.
web-design-analyzer
A web-design analysis helper that extracts colours, typography, and component patterns from a webpage screenshot, then produces structured design-system data and a coding prompt.
variant-analyze
When the user points to existing code (file paths, a directory, or says "analyze/audit/check my site"), switch from generation mode to analysis mode. Load references/design-system/style-audit.md for the full methodology and references/workflow/quality-baseline.md for shared mechanical and visual checks.