agentmods.dev

oh-my-design: Agent for Claude Code

.claude/agents/omd-persona-tester.md

omd-persona-tester is an agent for Claude Code from kwakseongjae/oh-my-design. It costs 75 tokens per session (1,309 once invoked), scanned A, original, MIT.

A synthetic user that tests a generated interface by following a task as a defined persona, such as an impatient user. It stops when its time or attempt limits are reached and records six measured results about success, effort and usability problems.

In plain words
What is it for?
Use it to test wireframes, labels, instructions and journeys with different personas. It produces feedback on task success, number of steps, extra effort, time to the first useful action, friction and rule violations.
Why use it?
It reveals where an interface fails for a realistic type of user instead of assuming the design is understandable. Its strict limits also prevent repeated attempts from hiding confusing steps.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is kwakseongjae/oh-my-design's own configuration. It tells Claude Code how to work on oh-my-design itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything oh-my-design configures →

not rated 500repo +15 5d ago A scan 75 tokens original MIT
View source ↗ kwakseongjae/oh-my-design oh-my-design.kr
Reuse

Borrowing it

Nothing to install: this file belongs to kwakseongjae/oh-my-design. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/kwakseongjae/oh-my-design/main/.claude/agents/omd-persona-tester.md
Clone the repo
git clone --depth 1 https://github.com/kwakseongjae/oh-my-design

Made for: Claude Code.

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 omd-persona-tester

README.md
[![agentmods](https://agentmods.dev/badge/agents/kwakseongjae/oh-my-design/omd-persona-tester/github.svg)](https://agentmods.dev/agents/kwakseongjae/oh-my-design/omd-persona-tester)
Your own site
<a href="https://agentmods.dev/agents/kwakseongjae/oh-my-design/omd-persona-tester"><img src="https://agentmods.dev/badge/agents/kwakseongjae/oh-my-design/omd-persona-tester/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 omd-persona-tester

Your own site · 80×15
<a href="https://agentmods.dev/agents/kwakseongjae/oh-my-design/omd-persona-tester"><img src="https://agentmods.dev/badge/agents/kwakseongjae/oh-my-design/omd-persona-tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,309 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 original No closer match found 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.00075 $0.01309
Opus 5 $0.00037 $0.00655
Sonnet 5 $0.00015 $0.00262
Haiku 4.5 $0.00007 $0.00131

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

Security

Grade A, and why

omd-persona-tester 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 13d 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.

.claude/agents/omd-persona-tester.md · 120 lines

How it starts

The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.

omd-persona-tester

You play a synthetic user testing a generated UI. You are NOT a helpful assistant — you are this persona. You ABANDON when limits are hit. You report failure honestly.

Inputs

The master invokes you once per persona. It passes:

  • persona_id: e.g. jeongmin / mr-lee / adversarial-impatient
  • persona_spec: full prompt block (see template below)
  • journey_path: the journey to walk
  • wireframes_dir: rendered wireframe set
  • microcopy_path: components/microcopy.json
  • assets_manifest: assets/manifest.json (so you can detect placeholder regions)
  • output_path: persona-feedback/<persona_id>.json

Persona prompt template (you become this)

You are <name>. <demographic>, <age>, <context>.
Your single goal in this session: <task>.
Your patience: <budget> seconds per step. After exceeding, you ABANDON.

Hard limits (absolute):
  - You will respond with literal "[ABANDON: <reason>]" if any limit is hit.
  - You will NOT pretend to understand jargon. If you don't get a label, mark friction.
  - You will NOT retry forever — one failure = ABANDON.

Friction triggers (count each occurrence):
  - I cannot find the next step within 5 seconds of looking.
  - Error messages don't tell me what to do.
  - The label uses jargon I don't know.
  - Anything appears broken / ugly / loading too long.
  - <persona-specific triggers>

Korean users specifically:
  - 즉시 가입 불가능하면 이탈
  - 계좌 인증/공인인증서 등장하면 이탈
  - 결제 직전에 회원가입 강요하면 이탈

Forbidden behaviors (you will NOT do these — they leak the LLM's helpful bias):
  - "Let me try again" loops
  - Praising the design
  - Speculating beyond what's on screen

Walkthrough protocol

If Playwright MCP available + a rendered URL exists

  1. Use mcp__playwright__browser_navigate to the URL.
  2. Use mcp__playwright__browser_snapshot to see the actual DOM.
  3. For each journey step, decide the persona's next click. Use mcp__playwright__browser_click with the element.
  4. Time each step (Bash date +%s%N). Cap by persona budget.
  5. Record actual click counts, actual time-to-first-meaningful-action.

Read the full file on GitHub · 120 lines

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. 13d ago First seen · 120 lines · 75 tokens per session scan A b15271ea1a44

Subscribe to this mod's changes

omd-persona-tester is an agent published in the GitHub repository kwakseongjae/oh-my-design (500 stars, last pushed 5d ago), licensed MIT. It adds 75 tokens to every session and 1,309 once invoked, about $0.0004 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.

E2E testingTestingclidesign-mddesign-systemdesign-tokensgoogle-stitchnextjs
Related

Other agents, from other repositories

test-gap-finder

Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.

HoangNguyen0403/agent-skills-standard · 37 tokens

frontend-specialist

A frontend verification agent that tests changed user-interface code in a real browser with Playwright, including screenshots for visual checks.

Insajin/autopus-adk · 61 tokens

e2e-tester

Tests web applications end-to-end by exercising real user flows and fixing verified code-level issues. Use when you want a full-app regression pass across critical flows such as forms, auth, AI features, import/export, and navigation. Reports infrastructure, environment, and product-level issues that require manual…

laguagu/claude-code-nextjs-skills · 84 tokens

e2e-runner

End-to-end testing specialist using Playwright. Generates, maintains, and runs E2E tests.

rohitg00/skillkit · 25 tokens

playwright-tester

Use Playwright MCP to write/maintain E2E tests; capture traces and screenshots for regression.

FortiumPartners/ensemble · 26 tokens

e2e-runner

Specialized agent that runs the full Playwright e2e suite in the project's Dockerized Chromium environment (docker-compose.e2e.yml) and reports pass/fail. Use before pushing to GitHub to guarantee e2e never regresses on main. Trigger on "run e2e", "e2e before push", "playwright check", or invoked by the pre-push git…

KaelSensei/MagicAIBuilder · 87 tokens