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/qte77/claude-code-plugins/auditing-website-usabilitynpx skills add qte77/claude-code-plugins --skill auditing-website-usabilitygit clone --depth 1 https://github.com/qte77/claude-code-pluginsWrote 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/qte77/claude-code-plugins/auditing-website-usability)<a href="https://agentmods.dev/skills/qte77/claude-code-plugins/auditing-website-usability"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/auditing-website-usability.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.00041 | $0.00728 |
| Opus 5 | $0.00020 | $0.00364 |
| Sonnet 5 | $0.00008 | $0.00146 |
| Haiku 4.5 | $0.00004 | $0.00073 |
Grade A, and why
auditing-website-usability 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Website Usability Audit
Target: $ARGUMENTS
Conducts focused usability audits and generates implementable UX fixes.
Complements auditing-website-accessibility (WCAG compliance) with
UX-focused analysis. No overlap: accessibility handles ARIA/contrast/keyboard;
this handles task completion, friction, and clarity.
Audit Areas
Forms
- Smart defaults and field reduction
- Logical grouping and progressive disclosure
- Inline validation with helpful messaging
Navigation
- Information architecture and menu depth (target: <3 levels)
- Mobile usability and touch targets
- Breadcrumbs, search, and task completion paths
Input Validation
- Real-time feedback and error prevention
- Clear error messages with recovery guidance
- Submission confirmation
Microcopy
- Button labels, form hints, and instructional text
- Error message clarity and actionability
- User confidence messaging
Workflow
- Identify scope from $ARGUMENTS (URL, file, or directory)
- Audit task flows - map primary user journeys, identify friction
- Inspect forms - field count, grouping, validation behavior
- Review navigation - menu depth, mobile patterns, findability
- Evaluate microcopy - labels, errors, guidance text
- Classify findings by impact on task completion
- Generate fixes with specific code changes
Output Format
Findings
CRITICAL (Task Completion Blockers)
- [Issue] - Impact: [High/Medium/Low] - Element: [selector]
Fix: [Specific code/design change]
Metric: [What improves - conversion, completion, error rate]
OPTIMIZATIONS (Friction Reduction)
- [Issue] - Impact: [High/Medium/Low] - Element: [selector]
Fix: [Specific code/design change]
Metric: [What improves]
Implementation Checklist
- [ ] [Fix description] - Impact: [High/Medium/Low]
Group fixes by: Forms, Navigation, Validation, Microcopy.
Rules
- Prioritize task-completion blockers before friction reduction
- Every finding must include a specific, implementable fix
- No time estimates -- prioritize by impact only
- Defer WCAG/accessibility concerns to
auditing-website-accessibility - Keep output concise: findings + fixes + checklist only
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 · 95 lines · 41 tokens per session scan A 00b8b0424721
auditing-website-usability is a skill published in the GitHub repository qte77/claude-code-plugins (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 41 tokens to every session and 728 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
brand
Give THIS project its own readable brand - after this, every chat card and /report in the project renders in the project's palette, logo, and font. Detects the identity from the repo (design tokens, tailwind config, DESIGN.md, logos) or interviews the user when none exists, then writes a committable .readable/ layer.…
open-design-guide
Use the Open Design content library: 151 design systems with real tokens (Apple, Vercel, Linear, Stripe, Notion, GitHub, Raycast, plus styles like brutalism and claymorphism), 71 design and frontend skills, and 114 rendering templates for decks, documents, video frames, and social cards. Use when building or restyling…
peekaboo
Provides runtime observation and interaction for native macOS interfaces through accessibility state and screenshots. Use when the task depends on visible or interactive state in a running SwiftUI/AppKit app: what is rendered, focused, selected, enabled, reachable through menus/windows/dialogs, or experienced across a…
electron-playwright-validator
This skill should be used when a user asks to launch, inspect, automate, test, validate, or debug an Electron desktop UI through Playwright/CDP, including blank renderers, runtime import failures, accessibility snapshots, layout defects, click-through flows, or post-change checks. Not for native macOS or mobile apps…
photo-pass
Run a conservative, end-to-end art-direction photo pass over a whole website: audit where photos genuinely earn their place, define one visual language, source free images, melt them into the design, verify in both themes, and record credits. Use when the user asks for a "photo pass", wants photography/warmth/imagery…
generate-doc-template
Generates on-brand document and deck templates — letterhead, slide, and one-pager — as SVG from the active brand profile, with editable title, subtitle, and body zones. Vector output needs no account, key, or network. Use when a user asks for a letterhead, a slide or deck master, or a branded one-pager. Trigger with…