Borrowing it
Nothing to install: this file belongs to muratgur/ordinus. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/muratgur/ordinus/master/.claude/skills/ordinus-ui-system/SKILL.mdgit clone --depth 1 https://github.com/muratgur/ordinusWrote 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/muratgur/ordinus/ordinus-ui-system)<a href="https://agentmods.dev/skills/muratgur/ordinus/ordinus-ui-system"><img src="https://agentmods.dev/badge/skills/muratgur/ordinus/ordinus-ui-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/muratgur/ordinus/ordinus-ui-system"><img src="https://agentmods.dev/badge/skills/muratgur/ordinus/ordinus-ui-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.00702 |
| Opus 5 | $0.00028 | $0.00351 |
| Sonnet 5 | $0.00011 | $0.00140 |
| Haiku 4.5 | $0.00006 | $0.00070 |
Grade A, and why
ordinus-ui-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 9d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ordinus UI System
Objective
Make Ordinus feel like a calm, practical command center for AI-assisted work.
Design System Source
Read DESIGN.md before changing renderer UI, layout, Tailwind styling, shadcn-style components, status surfaces, empty states, forms, task views, provider views, or user-facing product copy.
Treat DESIGN.md as the canonical source for visual tokens, component vocabulary, status language, density, and copy guidance. If it conflicts with AGENTS.md, the secure Electron boundary and product principles in AGENTS.md win.
Product Feel
- Work-focused, not marketing-focused.
- Clear status over decorative flourish.
- Dense enough for repeated use, but not crowded.
- User-facing text should describe product state and next actions, not internal implementation.
- Avoid turning the app into a generic chat page.
- Distinctive but calm. Ordinus should feel intentionally designed without becoming loud or theatrical.
Avoid Generic AI UI
- Do not default to generic assistant layouts, oversized prompt boxes, purple gradients, vague glowing panels, or decorative AI-themed backgrounds.
- Choose a clear product direction before styling: desktop command center, operational workspace, project cockpit, or agent control surface.
- Let the product context drive visual choices. Agent status, work progress, outputs, and attention states matter more than visual novelty.
- Use typography, spacing, color, and motion deliberately. The interface should feel polished because details are consistent, not because effects are abundant.
- Prefer subtle useful motion for state transitions, loading, reveal, and feedback. Avoid animations that distract from work.
- Make empty states, status labels, and action hierarchy feel designed, not placeholder-like.
UI Rules
- Align colors, typography, spacing, radius, status labels, and component naming with
DESIGN.md. - Use shadcn-style components and local reusable primitives.
- Prefer restrained cards for individual panels, not nested card-heavy layouts.
- Use lucide icons for recognizable actions.
- Keep typography readable and proportional to the UI surface.
- Avoid decorative gradients, orbs, bokeh, and oversized hero sections.
- Make status visible: planned, running, blocked, completed, needs attention.
- Avoid one-note palettes. Use a restrained base with purposeful accent colors for state and hierarchy.
- Match component density to the workflow: dashboards and work boards should be scan-friendly, not spacious landing pages.
What ships with it
1 file 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.
- 9d ago First seen · 64 lines · 55 tokens per session scan A 133e206bcb88
ordinus-ui-system is a skill published in the GitHub repository muratgur/ordinus (111 stars, last pushed 6d ago), licensed MIT. It adds 55 tokens to every session and 702 once invoked, about $0.0003 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
openforms-mui
Author, render, preview and debug OpenForms FormSchemaJSON form definitions as idiomatic, themed, accessible MUI (React). Use when the user wants to design an OpenForms form, render an OpenForms schema with Material UI, convert an OpenForms JSON schema into a React MUI form, preview a form schema, or debug…
canvas-webapp
Render a React/Vite (or any bundled) web app on the pi-dashboard canvas, which loads loopback URLs in a sandboxed opaque-origin iframe. Use when a canvas(target:{kind:"url"|"server"}) target shows up blank white, an empty surface, or a /live/ 500 ECONNREFUSED. Covers why Vite dev servers and non-CORS static servers…
ritual-dapp-frontend
Skill "ritual-dapp-frontend" from OpenCoven/coven, covering ritual dapp frontend skill, when to use, tech stack, quick start pattern and 1. setup chain & providers.
electron-expert
Expert in Electron framework, desktop app development, IPC, and cross-platform packaging. Use when the user mentions desktop, Node.js, cross platform, Windows, macOS, or Linux, or when the task involves Electron Architecture, Process Types, IPC Communication, or App Lifecycle.
artisan
Implementing production frontend code for React/Vue/Svelte: hooks design, state management, Server Components, form handling, data fetching. Converts Forge prototypes to production quality.
agent-user-interface
Batteries-included agent component for React/Next.js from ui.inference.sh. One component with runtime, tools, streaming, approvals, and widgets built in. Capabilities: drop-in agent, human-in-the-loop, client-side tools, form filling. Use for: building AI chat interfaces, agenti…