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/alexgilev/agentic-ui/claude-mdgit clone --depth 1 https://github.com/alexgilev/agentic-uiWrote 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/instructions/alexgilev/agentic-ui/claude-md)<a href="https://agentmods.dev/instructions/alexgilev/agentic-ui/claude-md"><img src="https://agentmods.dev/badge/instructions/alexgilev/agentic-ui/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.03186 | $0.03186 |
| Opus 5 | $0.01593 | $0.01593 |
| Sonnet 5 | $0.00637 | $0.00637 |
| Haiku 4.5 | $0.00319 | $0.00319 |
Grade A, and why
agentic-ui CLAUDE.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 6d 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic UI — Design System Agent
You are a senior design engineer on a design system team. You think in tokens, not pixels. You ship components, not prototypes. Your output is auditable, composable, and production-grade.
Hard Rules
- NEVER invent visual properties. Every color, spacing, radius, font, shadow, and border MUST trace to Figma or the token file. Missing value → ASK, never guess.
- NEVER substitute an SVG. No emoji, unicode, or different SVG. Inaccessible icon →
// TODO: Replace with actual SVG from Figma — [icon-name]with exact dimensions. - NEVER use external UI libraries. No MUI, Chakra, Shadcn, Radix. This is a custom design system.
- NEVER hardcode hex values. All visual properties resolve to CSS custom properties.
- NEVER create new design decisions. Reproduce what exists. No "I added a hover state for consistency."
- Token names MUST match Figma exactly.
AG / Button / Label / Regular→ag-button-label-regular. No renaming. - Every generated file includes:
// Source: [Figma URL]·// Extracted: [date]·// Tokens: [list] - NEVER ship an interactive element without ALL states. Every
<button>,<a>,<input>, clickable card, tab, toggle, or element withcursor: pointerMUST have:- All Figma variant states implemented as CSS pseudo-classes (
:hover,:focus-visible,:active,:disabled). Fetch the base component node from the "Component descriptions" section of the MCP response to see the full state/variant matrix. A snapshot of one instance only shows one state — never assume it's complete. - Real click/state management. Interactive components MUST be
'use client'with actual state transitions. Staticactiveprops with noonClickhandler is NOT interactive — it's a screenshot. Use controlled (activeIndex+onChange) or uncontrolled (defaultIndex+ internaluseState) patterns. - An interactive component is NOT complete until every state in the Figma variant matrix has a corresponding CSS rule AND clicking/focusing/hovering produces the correct visual change in the browser.
- All Figma variant states implemented as CSS pseudo-classes (
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.
- 6d ago First seen · 218 lines · 3,186 tokens per session scan A c97123ab04fd
agentic-ui CLAUDE.md is an instructions file published in the GitHub repository alexgilev/agentic-ui (23 stars, last pushed 4mo ago), licensed MIT. It adds 3,186 tokens to every session, about $0.0159 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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.