usability-test-plan

usability-test-plan is a skill for Claude Code from realmpastai-web/claude-design-suite. It costs 36 tokens per session (347 once invoked), scanned A, a copy of usability-test-plan, MIT.

A skill for planning usability tests, sessions where people try a design or prototype so a team can see what works and where users struggle. It defines participants, tasks, measurements, facilitation, and analysis.

In plain words
What is it for?
Use it to write research questions, recruit suitable participants, create realistic tasks, define success measures, guide sessions, record observations, and plan how findings will be prioritized.
Why use it?
It turns a general wish to test a design into a repeatable research plan. This helps the team collect comparable evidence instead of relying only on opinions.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the design-research plugin — 10 skills, 4 commands shipped together

Good fit Use it to write research questions, recruit suitable participants, create realistic tasks, define success measures, guide sessions, record observations, and plan how findings will be prioritized.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/realmpastai-web/claude-design-suite/usability-test-plan
Install

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.

Any agent
npx skills add realmpastai-web/claude-design-suite --skill usability-test-plan
Clone the repo
git clone --depth 1 https://github.com/realmpastai-web/claude-design-suite

Made for: Claude Code.

Or install design-research, the plugin that ships this one along with the rest of its 10 skills, 4 commands.

Wrote 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.

agentmods badge for usability-test-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/realmpastai-web/claude-design-suite/usability-test-plan/github.svg)](https://agentmods.dev/skills/realmpastai-web/claude-design-suite/usability-test-plan)
Your own site
<a href="https://agentmods.dev/skills/realmpastai-web/claude-design-suite/usability-test-plan"><img src="https://agentmods.dev/badge/skills/realmpastai-web/claude-design-suite/usability-test-plan/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.

agentmods 80×15 button for usability-test-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/realmpastai-web/claude-design-suite/usability-test-plan"><img src="https://agentmods.dev/badge/skills/realmpastai-web/claude-design-suite/usability-test-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 347 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 86% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.00347
Opus 5 $0.00018 $0.00173
Sonnet 5 $0.00007 $0.00069
Haiku 4.5 $0.00004 $0.00035

Measured 12d ago against content hash 83bf3856bb97, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

usability-test-plan 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.

Origin

This is a copy

86% identical to usability-test-plan — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/design-research/skills/usability-test-plan/SKILL.md · 33 lines

What it actually says

Usability Test Plan

Design a comprehensive usability test plan for evaluating designs and prototypes.

Context

You are a senior UX researcher designing a usability test plan for $ARGUMENTS. If the user provides files (prototypes, designs, personas), read them first.

Instructions

  1. Define objectives: What specific questions should this test answer?
  2. Create the test plan with:
    • Research questions: 3-5 specific questions to answer
    • Methodology: Moderated vs unmoderated, remote vs in-person, think-aloud protocol
    • Participants: Screening criteria, sample size (5-8 per segment), recruitment approach
    • Tasks: 5-8 realistic task scenarios with success criteria and expected completion time
    • Metrics: Task success rate, time on task, error rate, SUS/SEQ scores, satisfaction rating
    • Facilitation guide: Script for introduction, task delivery, probing, and debrief
    • Data collection: What to record, observation template, note-taking framework
    • Analysis plan: How findings will be synthesized and prioritized
  3. Include a pilot test checklist: What to verify before the real sessions.
  4. Think step by step. Present in a ready-to-use format.

Further Reading

  • Rocket Surgery Made Easy — Steve Krug
  • Measuring the User Experience — Tom Tullis and Bill Albert
Changes

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.

  1. 12d ago First seen · 33 lines · 36 tokens per session scan A 83bf3856bb97

Subscribe to this mod's changes

usability-test-plan is a skill published in the GitHub repository realmpastai-web/claude-design-suite (2 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 347 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to usability-test-plan, differing in 2 lines, and is treated as a copy.

Related

Other skills, from other repositories

qa-test-planner

Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.

davila7/claude-code-templates · 34 tokens

design-qa

Internal prototype QA helper. Use only after a Product Design prototype, URL-to-code build, or image-to-code build has a source visual target and a rendered implementation to compare before handoff. Do not use for broad UX critique, design critique, product audits, or flow reviews; route those user-facing requests to…

XiaomiMiMo/MiMo-Code · 68 tokens

health

Runs a budget-aware agent-assisted engineering health audit for instruction/config drift, hooks/MCP, verifier surfaces, and AI maintainability. Use when users ask in any language to audit Claude, Codex, Pi, agent instructions, MCP or hooks, verifier coverage, or AI-maintainability drift. Not for debugging application…

tw93/Waza · 71 tokens

hunt

Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code…

tw93/Waza · 70 tokens

chrome-cdp

Drive a headless Chrome over the Chrome DevTools Protocol (CDP) for browser QA — navigate, click, fill forms, read the DOM/accessibility tree, screenshot, and assert. Use whenever a task requires loading a web page and interacting with it like a user. Chrome is launched by a bash step (recipe below); this skill…

mattzcarey/shippie · 91 tokens

ui-craft-checks

Use this comprehensive gate for formal review, QA, launch handoff, exact-fidelity inspection, high-risk complex UI, or when the fast gate exposes a deeper craft problem. Ordinary single-screen work uses ui-design-executor and its bundled validator without loading this full matrix. Pair standalone artifacts with…

Orkas-AI/Orkas · 5 tokens