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 instructions/starc007/ui-components/agents-mdgit clone --depth 1 https://github.com/starc007/ui-componentsWhat 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.06500 | $0.06500 |
| Opus 5 | $0.03250 | $0.03250 |
| Sonnet 5 | $0.01300 | $0.01300 |
| Haiku 4.5 | $0.00650 | $0.00650 |
Grade A, and why
ui-components AGENTS.md 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 2d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
beUI v2 — agent guide
React motion component library plus its docs site, distributed as copy-paste source via shadcn-compatible registry endpoints. Stack: Next.js 15 (App Router), React 19, Tailwind CSS 4, motion (framer-motion) v11, TypeScript strict, Bun, Biome. Live at beui.dev.
Commands
bun install
bun run dev # local site
bun run typecheck # tsc --noEmit
bun run lint # biome
bun run check:registry # every registry component can publish its files
bun run check # all three — run before committing
Prefer typecheck + lint for quick verification. Do not start the dev server or run bun run build unless explicitly asked.
Layout
components/motion/andcomponents/agents/— the library. One file per component; multi-file widgets get a folder (swap/,button/,loading-states/).components/previews/— demo per component, registered incomponents/previews/index.tsx. Previews ship through the registry too. When an interactive preview uses internal demo helpers, set the registry entry'susageFileto a separate public composition so the Usage tab stays copyable.components/app/— site chrome (header, hero, dock, code blocks). Not part of the library.lib/registry.ts— component catalog (slugs, files, examples). Three categories:motion(display name "Components", primitives),agents(AI and agent interface primitives), andblocks(composed widgets: swap, dynamic island, command palette, expandable action bar). Blocks emitregistry:blockshadcn items. Preview files live undercomponents/previews/<category>/.lib/registry-server.tsbuilds registry items by following each file's@/and relative imports and bundling everything it finds. Internal imports are therefore safe and encouraged; a component that imports@/lib/easeshipslib/ease.tswith it.app/r/*— registry endpoints (shadcn items, raw source, index). beUI is listed in shadcn's official registry directory as the@beuinamespace with URL templatehttps://beui.dev/r/{name}.json— that path shape and existing install slugs are public contract; never break or rename them.lib/ease.ts— all motion tokens.scripts/check-registry.ts— validates the catalog.
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.
- 2d ago First seen · 160 lines · 6,500 tokens per session scan A 49f1e90957d2
ui-components AGENTS.md is an instructions file published in the GitHub repository starc007/ui-components (1,355 stars, last pushed 3d ago), licensed MIT. It adds 6,500 tokens to every session, about $0.0325 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 instructions, from other repositories
unity-ui-toolkit-design-system AGENTS.md
Instructions for sinanata/unity-ui-toolkit-design-system, covering agents.md, what this project is, golden rules (do not violate), use the design system in your project and repository layout.
unity-ui-toolkit-design-system copilot-instructions.md
Instructions for sinanata/unity-ui-toolkit-design-system: This repository follows the cross-tool AGENTS.md standard. Read /AGENTS.md for the full guide: the ds- class naming, the token rules, the load-bearing USS import order, build and preview commands, and the pull-request checklist.
ui CLAUDE.md
Claude Code instructions for persianlabs/ui, covering claude.md, what this is, commands, before pushing and architecture: components exist in two places, on purpose.
ui AGENTS.md
AGENTS.md instructions for persianlabs/ui, covering this is not the next.js you know, adding a new component or utility, component and utility previews, copyable page and .md endpoint and guard script.
forge AGENTS.md
Instructions for Webba-Creative-Technologies/forge, covering agents.md, rule 1: forge first, always, rule 2: single import source, rule 3: forgeprovider is required and rule 4: icons from fluent ui 2 only.
gradio AGENTS.md
AGENTS.md instructions for gradio-app/gradio, covering agents.md, repository structure, pull request rules, code style and agentic contribution policy.