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 skills/teamspwk/nova/ux-auditnpx skills add TeamSPWK/nova --skill ux-auditgit clone --depth 1 https://github.com/TeamSPWK/novaWrote 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/teamspwk/nova/ux-audit)<a href="https://agentmods.dev/skills/teamspwk/nova/ux-audit"><img src="https://agentmods.dev/badge/skills/teamspwk/nova/ux-audit.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.00067 | $0.05971 |
| Opus 5 | $0.00034 | $0.02985 |
| Sonnet 5 | $0.00013 | $0.01194 |
| Haiku 4.5 | $0.00007 | $0.00597 |
Grade A, and why
ux-audit 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 — 418 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nova UX Audit
5인 적대적 평가자(Adversarial Jury)로 UI/UX를 다관점 심층 평가한다. 각 평가자는 서로 다른 페르소나로 독립 분석하며, 결과를 종합하여 우선순위 개선 목록을 도출한다.
"사용자는 코드를 보지 않는다. 사용자가 보는 것만이 진실이다."
핵심 원칙
- 독립 평가: 5인 전원 독립 서브에이전트로 실행 (상호 영향 금지)
- 코드 기반: 실제 컴포넌트/i18n/스타일 코드를 읽고 분석 (추측 금지)
- 분석 전용: 평가자는 코드를 수정하지 않는다
- 최신 기준: WCAG 2.2, Core Web Vitals (INP), EU DSA 2024 기준 적용
옵션
| 플래그 | 동작 |
|---|---|
| (없음) | 5인 평가 + 종합 보고 |
--target <경로> |
평가 범위 지정 (기본: 프론트엔드 전체 자동 탐색) |
--screenshot |
Puppeteer로 실제 화면 캡처 후 평가 (dev 서버 실행 필요) |
--live <URL> |
Computer Use로 실제 브라우저에서 앱을 조작하며 평가 (예: --live http://localhost:3000) |
--sprint |
결과를 스프린트로 자동 분할 |
--fix |
Critical/High 자동 수정 제안 (사용자 승인 필요) |
--a11y |
접근성 평가자를 Full 모드로 강제 (WCAG 전 항목 검사) |
실행 플로우
Phase 1: 환경 분석
- 프론트엔드 기술 스택 감지 (React/Vue/Svelte/Angular/etc.)
--target지정 시 해당 경로, 미지정 시 프론트엔드 루트 자동 탐색- i18n 파일, 테마/디자인 토큰, 라우트 구조, 컴포넌트 디렉토리 파악
--screenshot시: dev 서버 기동 확인 → Puppeteer MCP로 주요 화면 캡처 (미설치 시 경고 후 코드 분석만 수행)--live <URL>시: Computer Use로 실제 브라우저에서 앱을 열고 인터랙션하며 평가 (아래 상세 참조)- 디자인 시스템 자동 감지 (평가자 3 Cognitive Load 디자인 항목 평가용):
- 스캔 우선순위 5단계:
- tailwind.config.{ts,js,mjs,cjs} (Tailwind preset 추출)
- theme.{ts,tsx,js} 파일 (root, src/, app/) — export 객체 파싱
- *.css 파일의 :root { --token-name: ... } CSS 변수
- design-tokens/*.{json,ts,js} 직접 토큰 정의
- packages/*/tokens/, packages/design-system/ (monorepo 케이스)
- 결과 구조 (tokenCatalog):
{ "detected": true, "sources": [{"type": "tailwind", "path": "..."}], "tokenCount": { "color": 7, "spacing": 6, "fontSize": 5 }, "tokens": { "color": [...], "spacing": [...] }, "components": ["Button", "Input", "Card"] } - 미감지 시:
{ "detected": false } - 평가자 3 (Cognitive Load) 컨텍스트 주입은 요약 형태: tokenCount + 카테고리별 첫 5개 토큰만 (전체 토큰 카탈로그 주입 금지 — 평가자 토큰 부담 최소화)
- 스캔 우선순위 5단계:
환경 분석 결과를 요약하여 표시한다:
[Nova UX Audit] 스택: {React 18 + TypeScript} | 대상: {src/components/} | 모드: {코드 분석 / 스크린샷 포함} | 디자인 시스템: {Tailwind + 토큰 18개 / 미정의}
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 · 418 lines · 67 tokens per session scan A 01ccd0e0c0fc
ux-audit is a skill published in the GitHub repository TeamSPWK/nova (2 stars, last pushed 4d ago), licensed MIT. It adds 67 tokens to every session and 5,971 once invoked, about $0.0003 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-31.
Other skills, from other repositories
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…
shiny-bslib
Build modern Shiny dashboards and applications using bslib (Bootstrap 5). Use when creating new Shiny apps, modernizing legacy apps (fluidPage, fluidRow/column, tabsetPanel, wellPanel, shinythemes), or working with bslib page layouts, grid systems, cards, value boxes, navigation, sidebars, filling layouts, theming…
stakeholder-brief
Write a one-page stakeholder brief translating design system health or status into business language. Trigger when someone says: stakeholder update, exec brief, leadership summary, status report for leadership, system status for non-designers, write a brief for the business, or anything about communicating design…
token-audit
Audit a design system's token definitions for naming violations, missing semantic tiers, and structural debt. This audits how tokens are defined and organised, NOT how they are consumed in code. Trigger when someone says: audit my tokens, token naming review, are my tokens consistent, token health check, review my…
codebase-index
Generate a pre-computed component index from a design system codebase — YAML infrastructure files containing a component inventory, relationship graph, and summary statistics that AI agents and MCP servers consume. This produces machine-readable index files in .ai/index/, NOT a health report or quality assessment.…