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/moasq/agentic-ship/ui-systemnpx skills add moasq/agentic-ship --skill ui-systemgit clone --depth 1 https://github.com/moasq/agentic-shipWhat 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 | $0.00064 | $0.01415 |
| Opus 5 | $0.00032 | $0.00707 |
| Sonnet 5 | $0.00013 | $0.00283 |
| Haiku 4.5 | $0.00006 | $0.00142 |
Grade A, and why
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 3d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI System
Downstream contract: paths like
src/andconvex/refer to the product workspace that adopts Agentic Ship, not this tool repo.
This skill implements the tokens, type, density, shape and themes selected in the
validated UI plan. Use visual-direction first for substantial interface work; a
coherent token system cannot rescue an unexamined composition by itself.
Two of its references are load-on-demand procedures of their own:
- Before adding any new piece of interface —
references/component-sources.md, the source matrix (shadcn / MagicUI / Aceternity / 21st / compose) with discovery, install and review procedure. Formerly thecomponent-pickerskill. - Before adding any image, illustration, icon, or 3D —
references/asset-pipeline.md, sourcing, treatment, download and performance rules. Formerly theasset-pipelineskill.
Why AI sites look identical
Four defaults frequently signal an unexamined visual system:
- The untouched shadcn neutral palette.
- Inter, Geist, Space Grotesk, or Poppins as the primary face.
rounded-lgon everything.- Violet-to-blue gradient on white.
Changing those four removes common residue, but does not prove the hierarchy, content, assets, responsive intent or composition are product-specific. The visual-direction rubric owns that review.
1. Tokens live in exactly one place
Tailwind v4 is CSS-first. There is no tailwind.config.js. Everything lives in
src/app/globals.css: palette values in the :root and .dark blocks, mapped to
Tailwind utilities by the @theme block in the same file. If a config file appears,
migrate its contents into that file and delete it.
Replacing the shipped palette has two equivalent routes — pick by who is driving:
- A human at a browser: generate with tweakcn, export the
CSS variables, paste them into the
:rootand.darkblocks. - An agent, headless: follow
references/palette-recipes.md— named, fully specified oklch palettes plus the derivation rules for building a new one from a single brand hue. No GUI in the loop, same paste target.
What ships with it
4 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.
- 3d ago First seen · 124 lines · 64 tokens per session scan A aaac84912a05
ui-system is a skill published in the GitHub repository moasq/agentic-ship (10 stars, last pushed 4d ago), licensed MIT. It adds 64 tokens to every session and 1,415 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-31.
Other skills, from other repositories
design-guide
Paperclip UI design system guide for building consistent, reusable frontend components. Use when creating new UI components, modifying existing ones, adding pages or features to the frontend, styling UI elements, or when you need to understand the design language and conventions. Covers: component creation, design…
Shade ShadCN install
Guardrails for running pnpm dlx shadcn@latest add in Shade — never overwrite existing components, fresh branch first, swap raw colours for semantic tokens after integrating. Trigger when the user proposes a shadcn add, or when a fresh ShadCN-shaped file lands in apps/shade/src/components/ui.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
author-component
Create or review Blazor components (.razor files) with correct architecture. USE FOR: writing new Blazor components that do NOT involve JavaScript interop, implementing parameters and EventCallback, RenderFragment slots, component lifecycle (OnInitializedAsync, OnParametersSet), async patterns, IAsyncDisposable…
obsidian-layout-adjustment
Workflow for working with the user on changing how Obsidian looks using CSS snippets. Use this whenever the user asks to restyle Obsidian, tune a vault's visual layout, adjust tabs, sidebars, note surfaces, properties, backlinks, graph panes, file explorer rows, icons, links, shadows, active states, or CSS snippets.…