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 chaxus/ran --skill ranuigit clone --depth 1 https://github.com/chaxus/ranWrote 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/chaxus/ran/ranui)<a href="https://agentmods.dev/skills/chaxus/ran/ranui"><img src="https://agentmods.dev/badge/skills/chaxus/ran/ranui/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/chaxus/ran/ranui"><img src="https://agentmods.dev/badge/skills/chaxus/ran/ranui.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.00087 | $0.02096 |
| Opus 5.5 | $0.00035 | $0.00838 |
| Sonnet 5.5 | $0.00017 | $0.00419 |
| Haiku 4.5 | $0.00009 | $0.00210 |
Grade A, and why
ranui 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 1mo 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ranui — web component library
Framework-agnostic Web Components (Custom Elements + Shadow DOM). Works in React,
Vue, Svelte, Solid, or plain JS. Each element is <r-*> and is used like native HTML.
Styling crosses the shadow boundary via CSS variables, ::part(), or the
per-instance sheet attribute (escape hatch).
Authoritative reference (read these for exact APIs — don't guess)
When ranui is installed in a project, its docs ship inside the package:
node_modules/ranui/docs/COMPONENTS.md— generated per-element API: every element's attributes, typed properties, events (withdetailshape), slots, and::part()names. This is the source of truth for props/events. Regenerated in the source repo vianpm run doc:api.node_modules/ranui/docs/DESIGN.md— design system rules (color states, spacing, motion, accessibility §7, pre-ship checklist).node_modules/ranui/docs/style-tokens-public.md— the CSS variable (theming token) catalog.
In the source repo (packages/ranui) there is also a deep CLAUDE.md (architecture,
builder internals, LESS conventions, testing) — not shipped in the npm package.
Import map
Per-component, tree-shakeable side-effect imports register the custom element:
import 'ranui/button'; // then use <r-button>
import 'ranui/modal';
import 'ranui/select';
import 'ranui/input';
import 'ranui/message'; // also exposes an imperative message API
import 'ranui/checkbox';
Available element subpaths: button icon image input message skeleton tab tabpane radar modal select progress player popover dropdown content loading colorpicker math checkbox card router route link.
The fluent DOM builder + reactivity (no custom-element registration):
import { Div, View, Span, Label, ButtonBuilder, signal, createEffect, EventManager, Style } from 'ranui/builder';
SSR helpers: import { defineSSR } from 'ranui/ssr-registry' (source) / ranui/ssr,
ranui/ssr-stream. Types: ranui/typings.
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.
- 1mo ago First seen · 162 lines · 87 tokens per session scan A 7988f9fb1d14
ranui is a skill published in the GitHub repository chaxus/ran (269 stars, last pushed 6d ago), licensed MIT. It adds 87 tokens to every session and 2,096 once invoked, about $0.0003 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-30.
Other skills, from other repositories
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json…
magic-ui
Use this skill when users want to add, customize, or troubleshoot Magic UI components in React/Next.js projects. It covers component selection, shadcn registry installation (@magicui/), integration patterns, and practical quality checks for accessibility and maintainability.
dile-components
Use when building or modifying UI with the Dile Components library (@dile/ui, @dile/crud, @dile/editor, @dile/utils, @dile/lib, @dile/iconlib, @dile/icons) — a framework-agnostic, Lit-based web component catalog. Trigger when installing/importing dile- custom elements, using tags like , , , building CRUD screens…
frontend-ui-design
Use when design and build production-grade UI components using React, Vue, or vanilla HTML/CSS. Create responsive layouts, design systems, and accessible interfaces. Use when designing and build production-grade ui components using react, vue, or.
figma
Complete guide for the Figma plugin — REST API access, real-time selection monitoring via CDP, and the figma-app interactive UI. Read this IMMEDIATELY when the user asks to work with Figma.
react-component-design
Designs or reviews React component APIs. Handles prop drilling decisions, composition patterns, controlled/uncontrolled contracts, and minimal public API surfaces for React 18+ TypeScript components. Invoked when creating new components, refactoring existing ones, or reviewing component contracts.