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/codebygarv/ai-skills/ui-auditornpx skills add codebygarv/Ai-skills --skill ui-auditorgit clone --depth 1 https://github.com/codebygarv/Ai-skillsWrote 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/codebygarv/ai-skills/ui-auditor)<a href="https://agentmods.dev/skills/codebygarv/ai-skills/ui-auditor"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/ui-auditor.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.00033 | $0.00548 |
| Opus 5 | $0.00016 | $0.00274 |
| Sonnet 5 | $0.00007 | $0.00110 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
ui-auditor 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 yesterday.
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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Audit a UI implementation (code, screenshot, or both) for visual consistency and design quality — spacing, alignment, hierarchy, and adherence to the project's existing design patterns.
When to Use
- After implementing or changing a UI, before it ships.
- Reviewing a screen/component that feels "off" but it's unclear why.
- Comparing a new UI against the rest of the app for consistency.
For narrower, deeper dives, pair with Responsive Checker, Accessibility Auditor, Design System Guardian, or UI Text Formatter — this skill covers general visual quality across all of those areas at a lighter level.
What to Analyze
- Spacing & alignment — inconsistent gaps, misaligned elements, uneven padding between visually-similar components.
- Visual hierarchy — is the most important element actually the most prominent? Does heading/body/caption sizing create clear scan order?
- Consistency with the rest of the app — does this screen reuse existing components/patterns, or does it quietly reinvent a button/card/input style that already exists elsewhere?
- Color & contrast usage — colors used with clear purpose (not decoratively inconsistent), sufficient contrast for readability.
- State coverage — does the UI account for empty, loading, error, and populated states, not just the "happy path" screenshot?
- Density & whitespace — is the layout too cramped or too sparse relative to the content's importance and the rest of the app's density?
Output Format
- Findings grouped by area (Spacing, Hierarchy, Consistency, Color/Contrast, State Coverage).
- Each finding: what's inconsistent/wrong, where (component/screen), and a concrete fix (exact spacing value, which existing component to reuse, etc.).
- Flag anything that's a design-system violation specifically, and note that Design System Guardian can do a deeper token-level pass if useful.
What ships with it
2 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.
- yesterday First seen · 38 lines · 33 tokens per session scan A af3021d1b2ae
ui-auditor is a skill published in the GitHub repository codebygarv/Ai-skills (25 stars, last pushed 16d ago), licensed MIT. It adds 33 tokens to every session and 548 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
bun-api
Bun runtime API reference for TypeScript scripts. Covers Bun.serve() HTTP/HTTP/2 server with routes and WebSockets, fetch() transport options, Bun.file(), Bun.write(), Bun.$() shell, Bun.spawn(), Bun.Glob, Bun.env, bun:sqlite, Bun.sql() for PostgreSQL/MySQL via DATABASEURL, Bun.s3 for S3-compatible storage, Bun.redis…
bun-cli
Bun CLI reference for package management, script running, testing, bundling, and compilation. Covers bun install/add/remove/update, bun run, bun test, bun build, bunx, bun patch, bun audit fix, bun dedupe, bun prune, bun why, bun pm, bun repl, bunfig.toml, bun.lock, workspace catalogs, isolated installs and the global…
deps-upgrade
Validate JavaScript/TypeScript dependency upgrades after an interactive or manual update. Establish the real delta from git, detect peer/engine/type conflicts, extract breaking changes, migrations and adoptable features from release notes, assess held-back or seemingly unused packages, and run verification gates.…
git-pr
PR and MR workflows for GitHub (gh) and GitLab (glab). Creation, review comment handling, thread resolution, review state queries, merging, cost-aware bot review rounds (GitHub: Copilot, CodeRabbit), and Copilot code review configuration (rulesets, custom instructions, billing). Use when creating PRs/MRs, addressing…
git-project
GitHub Projects (v2) setup and management via gh CLI + GraphQL: organize a repo's issues into epics with native sub-issues, drive a board Status flow (Todo -> In Progress -> Done), set Project Priority, classify with native issue Types (Task/Bug/Feature) instead of labels, scope work with milestones (incl. resolving…
git-ci
CI/CD status queries for GitHub Actions (gh) and GitLab CI (glab). Check pipeline status, failing jobs, workflow runs, job logs, and merge readiness. Use when checking CI status, debugging build failures, viewing job logs, watching pipeline progress, or configuring gh/glab CI read-only allowlists. Not for PR workflows…