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 SapienXai/AgentOS --skill agentos-ui-uxgit clone --depth 1 https://github.com/SapienXai/AgentOSWrote 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/sapienxai/agentos/agentos-ui-ux)<a href="https://agentmods.dev/skills/sapienxai/agentos/agentos-ui-ux"><img src="https://agentmods.dev/badge/skills/sapienxai/agentos/agentos-ui-ux/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/sapienxai/agentos/agentos-ui-ux"><img src="https://agentmods.dev/badge/skills/sapienxai/agentos/agentos-ui-ux.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 180 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00062 | $0.03480 |
| Opus 5 | $0.00031 | $0.01740 |
| Sonnet 5 | $0.00012 | $0.00696 |
| Haiku 4.5 | $0.00006 | $0.00348 |
Grade A, and why
agentos-ui-ux 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 5d 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentOS UI and UX
Build calm, dense, trustworthy operator surfaces. AgentOS is the human control layer over OpenClaw: the UI must make real runtime state, ownership, failures, recovery, and next actions immediately understandable.
Start with the existing system
- Read
AGENTS.mdanddocs/agentos-codex-skill.md. - Inspect the target surface and related components before designing anything new.
- Reuse
components/ui/*,cn, existing badges, buttons, dialogs, inputs, and mission-control patterns. - For dialog architecture, inspect
components/mission-control/mission-control-dialog-shell.tsxfirst. It is the canonical bounded-desktop/full-screen-mobile shell; inspectcomponents/mission-control/context-engine-dialog.tsxas a theme-aware example implementation and intentional multi-pane exception. - Keep all UI copy in English. Use real data and real actions; never add decorative controls that imply unavailable functionality.
Design-System-First Decision Gate
Every meaningful AgentOS UI change must follow this order:
- Identify the operator outcome and workflow.
- Inspect the existing product surface and its closest neighboring flows.
- Inspect existing interaction patterns and state/recovery behavior.
- Inspect existing layout patterns and responsive behavior.
- Inspect shared primitives in
components/ui/*. - Inspect global and product-surface semantic tokens.
- Reuse or extend the closest canonical pattern.
- Create a new visual primitive only when the requirement cannot be represented correctly by the existing system, and record why.
Never design a new visual system directly from a feature requirement. First derive the UI from the existing AgentOS design system, interaction patterns, semantic tokens, and product-surface architecture. A new feature does not justify a new visual language. When a shared pattern is inadequate, improve that pattern instead of creating a disconnected one-off implementation.
For a significant change, complete the lightweight AgentOS UI Decision record below before implementation. Tiny copy, spacing, or local bug fixes do not need a separate record.
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.
- 5d ago Changed · +156 lines 0d04935bcca9
- 10d ago First seen · 89 lines · 62 tokens per session scan A 358defc807db
agentos-ui-ux is a skill published in the GitHub repository SapienXai/AgentOS (100 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 3,480 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
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.
web-animation-design
Design and implement web animations that feel natural and purposeful. Use this skill proactively whenever the user asks questions about animations, motion, easing, timing, duration, springs, transitions, or animation performance. This includes questions about how to animate specific UI elements, which easing to use…
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
web-design-engineer
Build or redesign polished browser-rendered visual artifacts with HTML/CSS/JavaScript/React: pages, dashboards, prototypes, slide decks, animations, UI mockups, and data visualizations. Use for visual front-end creation, design-system exploration, design critique, or explicit browser acceptance / QA of a web artifact.…
component-search
Search 21st.dev component registry for production-ready React components. Finds components by natural language description, filters by framework and style system, returns ranked results with install instructions. Use when looking for UI components, finding alternatives to existing components, or sourcing design system…
generic-react-design-system
Complete design system reference for React applications. Covers colors, typography, spacing, component patterns, glassmorphism effects, GPU-accelerated animations, and WCAG AA accessibility. Use when implementing UI, choosing colors, applying spacing, creating components, or ensuring brand consistency.