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 instructions/dev-lou/pixelpilot/uiux-design-critiquegit clone --depth 1 https://github.com/dev-lou/PixelPilotWrote 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/instructions/dev-lou/pixelpilot/uiux-design-critique)<a href="https://agentmods.dev/instructions/dev-lou/pixelpilot/uiux-design-critique"><img src="https://agentmods.dev/badge/instructions/dev-lou/pixelpilot/uiux-design-critique.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.02224 | $0.02224 |
| Opus 5 | $0.01112 | $0.01112 |
| Sonnet 5 | $0.00445 | $0.00445 |
| Haiku 4.5 | $0.00222 | $0.00222 |
Grade A, and why
PixelPilot uiux-design-critique.instructions.md 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 — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI/UX Design Critique Skill
Perform structured heuristic evaluation of UI/UX designs. Based on Nielsen's 10 heuristics + design language consistency.
OVERVIEW
This skill provides a systematic framework for evaluating user interfaces. Use it to:
- Conduct heuristic evaluations
- Identify usability issues
- Prioritize fixes by severity
- Ensure design language consistency
NIELSEN'S 10 USABILITY HEURISTICS
1. Visibility of System Status
Definition: The system should always keep users informed about what is going on through appropriate feedback within reasonable time.
Check for:
- Loading indicators on async operations
- Progress bars for multi-step processes
- Success/error feedback after actions
- Current state indicators (active nav, selected items)
Violations:
- Button clicked but no visual feedback
- Form submitted with no confirmation
- Background process with no indicator
- No "you are here" in navigation
Severity Guide:
- 🔴 Critical: User cannot tell if action succeeded
- 🟠 Major: Feedback exists but is unclear
- 🟡 Minor: Feedback is delayed or subtle
2. Match Between System and Real World
Definition: The system should speak the users' language with words, phrases, and concepts familiar to the user.
Check for:
- User-friendly language (not developer jargon)
- Familiar icons and metaphors
- Logical information order
- Cultural appropriateness
Violations:
- Error codes instead of explanations
- Technical terms without context
- Unfamiliar icons without labels
- Date formats wrong for locale
3. User Control and Freedom
Definition: Users often make mistakes and need clearly marked "emergency exits" to leave unwanted states.
Check for:
- Undo/redo functionality
- Cancel buttons on forms
- Back navigation that works
- Easy logout/exit options
- Confirmation before destructive actions
Violations:
- No way to cancel mid-process
- Cannot undo accidental deletion
- Trapped in modal with no exit
- Forced to complete unwanted flow
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 · 410 lines · 2,224 tokens per session scan A d5ecbf66c3bd
PixelPilot uiux-design-critique.instructions.md is an instructions file published in the GitHub repository dev-lou/PixelPilot (2 stars, last pushed 5mo ago), licensed MIT. It adds 2,224 tokens to every session, about $0.0111 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 instructions, from other repositories
arai CLAUDE.md
Instructions for taniwhaai/arai, covering claude.md — arai, commands, architecture, prompt-collector module (src/promptcollector.rs) and extending the match pipeline.
healthcare-agents AGENTS.md
Instructions for ajhcs/healthcare-agents, covering healthcare agents repository instructions, repository map, git workflow and self-improvement loop.
arai AGENTS.md
Instructions for taniwhaai/arai, covering agents.md — arai, core discipline (non-negotiable), taniwha / subagent rules, work style and tool usage.
shenzjd-skills CLAUDE.md
Claude Code instructions for wu529778790/shenzjd-skills, covering claude.md, project overview, commands, a single skill's unit test and architecture.
ui-ux-design-pro-skill CLAUDE.md
Instructions for saifyxpro/ui-ux-design-pro-skill, covering project overview, cli commands, full design system generation (markdown output), search across all databases (sub-50ms) and audit ui code quality.
syncai copilot-instructions.md
Instructions for dmtrkzntsv/syncai, covering claude.md, build & run, architecture, lifecycle and identify is the routing decision.