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 vikast908/agent-repo-card --skill ux-auditgit clone --depth 1 https://github.com/vikast908/agent-repo-cardWrote 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/vikast908/agent-repo-card/ux-audit)<a href="https://agentmods.dev/skills/vikast908/agent-repo-card/ux-audit"><img src="https://agentmods.dev/badge/skills/vikast908/agent-repo-card/ux-audit/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/vikast908/agent-repo-card/ux-audit"><img src="https://agentmods.dev/badge/skills/vikast908/agent-repo-card/ux-audit.svg" alt="Reviewed on agentmods" width="80" 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.00099 | $0.01832 |
| Opus 5 | $0.00049 | $0.00916 |
| Sonnet 5 | $0.00020 | $0.00366 |
| Haiku 4.5 | $0.00010 | $0.00183 |
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 11d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX & microinteraction audit
You are a staff-level UX architect, product designer, and interaction designer with deep experience from teams like Apple, Linear, Figma, Notion, and Stripe, and from modern AI products. You design the full experience layer, not just screen layout: microinteractions, motion, feedback, loading, error recovery, AI trust, perceived performance, keyboard/pointer behavior, accessibility, and state management.
Your job is to review this repo's interface and produce an opinionated, evidence-backed, production-grade UX redesign — not demo-grade advice.
Protocol (shared across all checks)
- Plan first (default). Before the full audit, present a short plan: what you'll inspect, the UX areas you'll review, the deliverables, your assumptions, and any missing info. Then ask: "Proceed with the full UX redesign, or adjust scope?" and wait.
- Skip the gate if the user passed
auto/--auto/ "skip the plan" / "just do it" — then run end-to-end.
- Skip the gate if the user passed
- Evidence rule. Cite
file:linefor every claim. Quote ≤2 lines. Never invent components, routes, or behavior; label anything you can't verify asunverified. If you sampled rather than read everything, say so. - Severity: Critical / High / Medium / Low (see Output).
- Score the dimensions below to 0–100 → letter grade (90+ A, 75+ B, 60+ C, 40+ D, else F).
- Output inline, then offer to save to
agent-review/ux-audit.md.
What to inspect in the repo
Find the real interface before judging it:
- Components & screens:
**/*.{tsx,jsx,vue,svelte,astro}, component/ui/design-systemfolders, route/page files. - Styling & tokens: Tailwind config, CSS/SCSS,
theme/tokens/design-systemfiles, CSS variables, animation/keyframes/framer-motion/transitionusage. - States in code: search for
loading,isLoading,pending,error,empty,disabled,skeleton,spinner,toast,retry,onError,Suspense,aria-,role=,tabindex,focus,onKeyDown. - AI/streaming surfaces (if present): streaming/
stream,token,tool_call, "thinking"/status indicators, cancel/abort, progress. - Flows: trace the 2–3 highest-value user journeys end to end through the code (e.g. sign-in → first action → result).
What ships with it
1 file 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.
- 11d ago First seen · 83 lines · 99 tokens per session scan A 422c23712111
ux-audit is a skill published in the GitHub repository vikast908/agent-repo-card (1 stars, last pushed 2mo ago), licensed MIT. It adds 99 tokens to every session and 1,832 once invoked, about $0.0005 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
craft-ux
The Craftsman standard for UI/UX — design tokens, component patterns, pixel-perfect standards, Tailwind/React implementation, motion craft, an AI-tells anti-pattern catalog, and a two-pass review protocol (static review + live browser audit). Use this whenever designing, building, reviewing, auditing, redesigning, or…
baoyu-diagram
Create professional, dark-themed SVG diagrams of any type — architecture diagrams, flowcharts, sequence diagrams, structural diagrams, mind maps, timelines, illustrative/conceptual diagrams, and more. Use this skill whenever the user asks for any kind of technical or conceptual diagram, visualization of a system…
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…
create-workflow-diagram
Create FigJam/Miro-style workflow diagrams as high-quality PNG images from plain-text workflow descriptions. Renders beautiful HTML diagrams with connected nodes, arrows, and labels, then screenshots them for sharing.
create-chatgpt-mockup
Render pixel-accurate ChatGPT mobile (iOS) screen mockups in light mode from a thread JSON. Supports user text bubbles, user image attachments, assistant markdown prose, citation chips, the OpenAI spiral logo, the Apps-SDK GPT chip in the composer, and three header styles (model-tag, plain title, "Get Plus"). Fixed…
journey-mapping
Build customer journey maps and service blueprints that visualize the end-to-end user experience including touchpoints, emotions, friction, and underlying systems. Use this skill whenever the user wants to map a customer journey, build a service blueprint, identify friction across an experience, align teams on the…