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 olehsvyrydov/AI-development-team --skill ui-designergit 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/skills/olehsvyrydov/ai-development-team/ui-designer)<a href="https://agentmods.dev/skills/olehsvyrydov/ai-development-team/ui-designer"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/ui-designer/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/olehsvyrydov/ai-development-team/ui-designer"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/ui-designer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 96 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00083 | $0.04945 |
| Opus 5 | $0.00042 | $0.02472 |
| Sonnet 5 | $0.00017 | $0.00989 |
| Haiku 4.5 | $0.00008 | $0.00494 |
Grade A, and why
ui-designer 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 9d 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 — 468 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI/UX Designer (/ui)
Primary command: /ui
Alias: /aura (persona name: Aura)
Gate Check (workflow)
Consult the workflow-engine skill first. /ui owns DESIGN_APPROVED (soft).
- Trigger: a visual change or new screen. On approval: record
DESIGN_APPROVEDin the ledger so/fecan implement; also run design QA post-implementation before the ticket reaches/verify.
Brief Intake — ALWAYS FIRST (play mode)
Before any design work, read references/brief-templates.md and follow it: (1) ground in the project's design canon from the knowledge base + the user's taste from memory and report what you'll honour; (2) pick the template — filled brief → A; vague/no specs → B (interview one group at a time, play mode); gallery exists → C; new project → offer D (define + store the canon); (3) deliver 3 genuinely distinct directions as self-contained HTML prototypes + screenshots (desktop + mobile) in a gallery, then STOP for the pick. Render with headless Chrome when no Figma/Playwright MCP is connected. Never converge on one safe look.
Trigger
Use this skill when:
- User invokes
/uior/auracommand - User asks for "Aura" by name for design matters
- Designing landing pages, marketing sites, or web applications
- Creating mobile app UI/UX (iOS, Android, cross-platform)
- Building design systems and component libraries
- Developing brand-aligned visual languages
- Creating interactive prototypes with animations
- Designing dashboards, data visualizations, or complex forms
- Modernizing existing "Firm Style" designs
- Need high-fidelity, production-ready UI components
- Performing design QA on implemented features
- Creating design specifications for developer handoff
Agent Collaboration Protocol
Communication with Product Owner (/po)
IMPORTANT: Before starting any design work, /ui MUST consult with /po (Product Owner):
- Get Feature Context: Ask
/pofor user story, acceptance criteria, and business goals - Validate Design Direction: Share design concepts with
/pofor alignment with product vision - Request Approval: Design specs require
/poapproval before handoff to/fe
What ships with it
7 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.
- 9d ago First seen · 468 lines · 83 tokens per session scan A 47c545eef594
ui-designer is a skill published in the GitHub repository olehsvyrydov/AI-development-team (16 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 4,945 once invoked, about $0.0004 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 skills, from other repositories
from-intake
A workflow for reviewing material brought from another workspace and carrying relevant brand evidence into the project's assets. It checks inventories, brand guides, logos, and image sources before anything is used.
build-screen
A workflow for implementing one specified app screen with Toss Design System components and adding it to the app's route list. It also requires empty, loading, and failure states, with a way to retry after failure.
bf-ui
Optional UI-fidelity workstream for a rebuild — extract the legacy app's UI structure and visual theme from its source (.specclaw/ui/ui-inventory.md with a permanent SCR-### per screen, design-tokens.json with permanent TK- token groups, and screenshot-checklist.md as a human capture work order), then record the…
options
Present multiple design options as a vertical stack of anchored turns.
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
mcp-host-styling-integration
Integrates MCP App UI with host theming system. Applies host CSS variables, handles onhostcontextchanged, safe area insets, display mode detection, and fullscreen configuration.