Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/gotempsh/tempsnpx agentmods add skills/gotempsh/temps/temps-design-systemWrote 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/gotempsh/temps/temps-design-system)<a href="https://agentmods.dev/skills/gotempsh/temps/temps-design-system"><img src="https://agentmods.dev/badge/skills/gotempsh/temps/temps-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/gotempsh/temps/temps-design-system"><img src="https://agentmods.dev/badge/skills/gotempsh/temps/temps-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.00148 | $0.02359 |
| Opus 5 | $0.00074 | $0.01179 |
| Sonnet 5 | $0.00030 | $0.00472 |
| Haiku 4.5 | $0.00015 | $0.00236 |
Grade A, and why
temps-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 today.
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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Temps design system
The design system is a sandbox app plus a component package. Everything a UI task needs is in the repo; do not invent tokens, colours or page shapes.
| What | Where |
|---|---|
| Rules digest for agents (read first, imperative, short) | design-system/docs/RULES.md |
| Brand guidelines (why the rules exist) | design-system/docs/brand-guidelines.md |
| Handoff: tokens, primitive catalogue, page templates, responsive, keyboard | design-system/docs/design-system-handoff.md |
| Component package consumed by screens | web/packages/ds (@temps-sdk/ds) |
Consumer setup (a plugin, an outside app): install, op.css, @source, the skin class, fonts |
web/packages/ds/README.md |
| Reference implementation of every screen | design-system/src/sections/ConsoleV1*.tsx |
| Browsable guide, component gallery, console mockups | cd design-system && bun install && bun run dev → /guide, /op-components, /v1 |
Scope boundary
What exists today, stated plainly so nobody assumes more: the production
console (web/src, rsbuild) does not import @temps-sdk/ds yet. What is
built is the system (the docs), the package, and the sandbox that renders every
primitive and every screen shape against it. Console migration happens screen by
screen, on a schedule, not as a side effect of another task.
- Redesign work (new screens on
@temps-sdk/ds, the sandbox, the landing and status page mockups): this skill applies in full. - Legacy console (
web/src/**on shadcn/ui): follow the frontend rules inCLAUDE.md. Do not restyle legacy screens piecemeal to the new system; a screen moves to the new system whole, when its migration is scheduled. - Plugin UI (a separate document in an iframe): see "Plugin UI" below. It gets the system by bundling the package, not by inheriting anything.
- The package (
web/packages/ds): change a primitive only together with its entry in the handoff doc §6, the gallery on/op-componentsand theCHANGELOG.mdof the package.
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.
- today First seen · 168 lines · 148 tokens per session scan A 1a629e0b0ec5
temps-design-system is a skill published in the GitHub repository gotempsh/temps (728 stars, last pushed today), licensed Apache-2.0. It adds 148 tokens to every session and 2,359 once invoked, about $0.0007 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-09-08.
Other skills, from other repositories
ss-lint
Quick automated lint — detects common design system violations in seconds.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
design-standards
Apply production-grade design standards when building or reviewing pages, components, or UI. Use this skill whenever the user asks to build a page, design a component, lay out a section, review the UI, fix the layout, or check design quality. Triggers on build a page, create a component, design a section, hero, card…
ln-75-architecture-diagram-builder
Creates current or target architecture diagrams as the primary deliverable. Not for UI design, architecture audits, or invented structure.
review-ui-platform
Normative reviewer for IntelliJ UI, Action System, ToolWindow, DialogWrapper, JCEF, accessibility and UI state consistency in the explyt spring-plugin. Use during orchestrated code review when the diff touches actions, tool windows, dialogs, settings panels, wizard steps, notifications, popups, renderers, icons or…
polish-ui
Design-quality workflow that combines design taste, aesthetic direction, image-to-code, a Web Interface Guidelines audit, and real-browser verification. Use when building or polishing a UI surface, implementing a mockup/screenshot, or when asked to make a page "look great".