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.
git clone --depth 1 https://github.com/nyldn/claude-dolphinWrote 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/nyldn/claude-dolphin/ui-audit)<a href="https://agentmods.dev/commands/nyldn/claude-dolphin/ui-audit"><img src="https://agentmods.dev/badge/commands/nyldn/claude-dolphin/ui-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.1 | $0.00011 | $0.01079 |
| Opus 5 | $0.00005 | $0.00540 |
| Sonnet 5 | $0.00002 | $0.00216 |
| Haiku 4.5 | $0.00001 | $0.00108 |
Grade A, and why
ui-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 7d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Audit Command
Perform a systematic UI audit on the specified scope.
Scope options:
- File path (e.g.,
src/components/ui/button.tsx) - Component name (e.g.,
Button) - Page path (e.g.,
src/app/dashboard/page.tsx) systemfor full codebase audit
Audit Process
Step 1: Scope Identification
Identify all UI-related files in the specified scope:
# Find component files
Glob: **/*.tsx, **/*.jsx in scope directory
# Find style files
Glob: **/*.css, **/*.scss in scope directory
# Find type definitions
Grep: interface.*Props in scope
Step 2: Accessibility Audit (WCAG 2.2 AA)
For each component, check:
Visual Accessibility:
- Color contrast ratios meet minimums (4.5:1 body, 3:1 large text)
- Focus states visible (2px+ outline, high contrast)
- Touch targets >= 44×44px for interactive elements
- No color-only information conveyance
Semantic Accessibility:
- Proper heading hierarchy (no skipped levels)
- Form labels associated with inputs (htmlFor/id match)
- Button vs link distinction appropriate
- Alt text on images (empty for decorative)
Interactive Accessibility:
- Keyboard navigable (tabIndex, handlers)
- ARIA labels where semantic HTML insufficient
- Loading/error states announced (aria-live)
- No keyboard traps
Step 3: Design Consistency Audit
Compare against project design system:
Design Tokens:
# Check for hardcoded colors
Grep: #[0-9a-fA-F]{3,6}|rgb\(|hsl\( in scope
# Check for hardcoded spacing
Grep: \d+px(?!.*var\() in scope
- Colors from design token palette
- Spacing from consistent scale (4, 8, 16, 24, 32, 48, 64px)
- Typography from defined scale
- Border radius consistent
Component Patterns:
- Using shadcn components where applicable
- Consistent button variants and sizes
- Uniform input/form styling
- Card/container patterns followed
Step 4: Usability Review
Evaluate user experience quality:
- Visual hierarchy clear (primary action obvious)
- Information architecture logical
- Error states helpful (not just "Error occurred")
- Loading states present for async operations
- Empty states designed (not just blank)
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.
- 7d ago First seen · 167 lines · 11 tokens per session scan A 8a8efde23dd6
ui-audit is a command published in the GitHub repository nyldn/claude-dolphin (9 stars, last pushed 14d ago), licensed MIT. It adds 11 tokens to every session and 1,079 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-31.
Other commands, from other repositories
anti-slop-designer
Use when a UI looks machine-made rather than decided. Violet gradients, glassmorphism everywhere, identical cards in a grid, untouched shadcn or Material defaults, emoji bullets, or copy stuffed with seamless and unlock.
svg-create
Author or clean up an SVG asset — icon, illustration, mascot pose, logo mark — so it scales from viewBox, recolors from tokens, animates without a rewrite, is optimized, and has an accessible name.
agentation-fix
Session-2 fix loop for Agentation — read structured annotations from the dev overlay and apply targeted UI fixes.
scan-ai-tells
Scan UI or marketing copy for AI-default tells and content-authenticity misses — deletion list, not a redesign brief.
style-guide
Generate comprehensive design system documentation including colors, typography, spacing, components, and usage guidelines. Outputs production-ready Tailwind/CSS configuration.
design-critic
Use when you want an honest read on a design instead of encouragement. What is wrong, ranked by severity, with the reason attached. Works on a screenshot, a mockup, or a described screen.