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 mshadmanrahman/claude-for-designers --skill heuristic-evaluationgit clone --depth 1 https://github.com/mshadmanrahman/claude-for-designersWrote 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/mshadmanrahman/claude-for-designers/heuristic-evaluation)<a href="https://agentmods.dev/skills/mshadmanrahman/claude-for-designers/heuristic-evaluation"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/claude-for-designers/heuristic-evaluation/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/mshadmanrahman/claude-for-designers/heuristic-evaluation"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/claude-for-designers/heuristic-evaluation.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.00039 | $0.00646 |
| Opus 5 | $0.00019 | $0.00323 |
| Sonnet 5 | $0.00008 | $0.00129 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
heuristic-evaluation 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 12d 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.
What it actually says
You are running a structured usability audit. Do not produce a general list of suggestions. Every finding must reference something specific and visible in the design the student has shared.
Ask the user to provide: (1) the design output (HTML file, Figma link, or screenshot), and (2) the target user and their primary task. If either is missing, ask for it before starting.
Review against Nielsen's 10 usability heuristics. For each heuristic, give:
- Rating: Pass / Needs work / Fail
- Evidence: one specific example from this design. Name the element, the screen, the exact behaviour
- Fix: one concrete recommendation (not "improve feedback", but "add a spinner to the Submit button when the form is processing so the user knows the action was received")
1. Visibility of system status Does the interface always tell the user what is happening? Are loading states, success states, and error states communicated in real time?
2. Match between system and real world Does the language match what the user already knows? Are icons and metaphors familiar? Does the flow follow conventions the user has encountered elsewhere?
3. User control and freedom Can the user undo, go back, or exit without being punished? Are there clear escape routes from every state?
4. Consistency and standards Do similar elements behave the same way across the product? Does the design follow platform conventions (mobile tap targets, web link underlines, form field labels)?
5. Error prevention Does the design prevent mistakes before they happen? Are destructive actions protected by confirmation? Are required fields marked before submission?
6. Recognition over recall Does the user have to remember things from one screen to apply them on another? Are options visible rather than requiring the user to type them from memory?
7. Flexibility and efficiency of use Can an experienced user move faster? Are there shortcuts, filters, or bulk actions for power users that do not get in the way of first-time users?
8. Aesthetic and minimalist design Does every element on screen serve the current task? Is there anything the user has to process that does not help them complete their goal?
9. Help users recognise, diagnose, and recover from errors Are error messages in plain language? Do they name the problem, explain why it happened, and tell the user exactly what to do next?
10. Help and documentation If a user gets stuck, is there a clear path to help? Are tooltips, empty states, and onboarding written to answer the most common question, not to fill space?
After all ten heuristics, give a summary:
- Total counts: Pass / Needs work / Fail
- Priority fix list: Fail items first, Needs work second, ordered by user impact
- One sentence on the biggest risk if this ships without changes
Do not soften findings. A Fail is a Fail.
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.
- 12d ago First seen · 51 lines · 39 tokens per session scan A 390944417947
heuristic-evaluation is a skill published in the GitHub repository mshadmanrahman/claude-for-designers (28 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 646 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-08-30.
Other skills, from other repositories
brand-identity
Brand strategy and identity design for businesses and products. Use when creating brand guidelines, developing visual identity systems, or defining brand positioning.
graphic-design
Professional graphic design principles for digital and print media. Use when creating visual designs, choosing color palettes, typography, layouts, or providing design feedback.
generic-react-ux-designer
Professional UI/UX design expertise for React applications. Covers design thinking, user psychology (Hick's/Fitts's/Jakob's Law), visual hierarchy, interaction patterns, accessibility, performance-driven design, and design critique. Use when designing features, improving UX, solving user problems, or conducting design…
frontend-enhancer
This skill should be used when enhancing the visual design and aesthetics of web applications. It provides modern UI components, design patterns, color palettes, animations, and layout templates. REQUIRES ui-research skill first. Use this skill for tasks like improving styling, creating responsive designs…
generic-design-system
Complete design system reference for any project - colors, typography, spacing, components, animations. Adapts to project theme and tech stack. Use when implementing UI, choosing colors, creating animations, or ensuring brand consistency. For new design systems, use ui-research skill first.
generic-react-design-system
Complete design system reference for React applications. Covers colors, typography, spacing, component patterns, glassmorphism effects, GPU-accelerated animations, and WCAG AA accessibility. Use when implementing UI, choosing colors, applying spacing, creating components, or ensuring brand consistency.