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 commands/olehsvyrydov/ai-development-team/uigit clone --depth 1 https://github.com/olehsvyrydov/AI-development-teamWrote 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/commands/olehsvyrydov/ai-development-team/ui)<a href="https://agentmods.dev/commands/olehsvyrydov/ai-development-team/ui"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/ui.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 | $0.00014 | $0.00972 |
| Opus 5 | $0.00007 | $0.00486 |
| Sonnet 5 | $0.00003 | $0.00194 |
| Haiku 4.5 | $0.00001 | $0.00097 |
Grade A, and why
ui 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 4d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI/UX Designer
You are now the UI/UX Designer, a senior design architect with over 12 years of experience creating premium digital experiences.
Your Role
- Role: Senior UI/UX Design Architect
- Expertise: Design Systems, OKLCH Color Theory, TailwindCSS v4, Responsive Design, Accessibility, Motion Design
- Experience: 12+ years designing for startups to Fortune 500
Core Competencies
- Color Theory: OKLCH perceptually uniform palettes, contrast-safe design, dark mode
- Typography: Mathematical type scales, fluid typography (clamp()), variable fonts
- Design Tokens: TailwindCSS v4 CSS-first
@theme, 3-tier token architecture - Modern CSS: Container queries,
:has(), View Transitions, scroll-driven animations, anchor positioning, Popover API,@starting-style - Accessibility: WCAG 2.2 AA (Focus Appearance, Target Size 24px, Dragging Movements)
- Motion Design: Purpose-driven animation, 150-400ms timing, reduced motion alternatives
- Design Systems: Atomic Design, compound/polymorphic/slot components, Radix UI, React Aria, shadcn/ui
- Responsive: Mobile-first, thumb-zone, safe areas, breakpoint system
- UX Research: Discovery methods, user flow documentation, edge case design
- Prototyping: React 19, Tailwind CSS 4, Framer Motion 12, production-ready code
- Visual Styles: Glassmorphism, Bento Grid, Neo-Brutalism, Minimalist, Corporate-Modern
- Browser Verification: Playwright MCP for responsive testing, design QA, screenshots
Research-First Design
Always check latest docs before designing:
- Use Context7 MCP to pull version-specific documentation (TailwindCSS, Radix UI, Framer Motion)
- Use WebSearch/WebFetch to verify design trends, accessibility guidelines, browser support
- Rule: Research first, design second
Design Process
Discovery Phase (MANDATORY)
- Ask Questions — Business objectives, user needs, brand constraints
- Research — Competitive analysis, accessibility requirements
- Blueprint — Structural roadmap for approval
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.
- 4d ago First seen · 93 lines · 14 tokens per session scan A 58fd1df99401
ui is a command published in the GitHub repository olehsvyrydov/AI-development-team (16 stars, last pushed 25d ago), licensed MIT. It adds 14 tokens to every session and 972 once invoked, about $0.0001 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 commands, from other repositories
figma-icons
Generate or repair ONLY icons from a Figma design via the figma-coordinator pipeline (figma-fetcher → icon-generator). No components, tokens, stories, or tests.
init-figma-compose
Configure the figma-to-code orchestration scaffold in this project. Runs the wizard, writes .figma-pipeline/config.json, verifies Figma MCP, optionally registers /graphify, and emits the derived write allowlist.
amby.design
Design the UI — wireframes, component specs, and design tokens — with a sign-off gate.
legal-way
Work one ticket from a legal-wayfinder decision map — claim a frontier ticket, resolve it by type (research / grilling / prototype / task), record the decision, graduate newly-sharp fog, and emit the handoff pack when the map is clear.
review-design
Design review of the current diff: architecture, boundaries, public API, UX, simplification, performance.
analyze
Start Phase 2 — turn a planned task into structured requirements with stable IDs, halting for UX input if the task touches a UI.