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.
git clone --depth 1 https://github.com/MN-Lizard-Team/aiyu-multi-agentWrote 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/rules/mn-lizard-team/aiyu-multi-agent/ux-researcher)<a href="https://agentmods.dev/rules/mn-lizard-team/aiyu-multi-agent/ux-researcher"><img src="https://agentmods.dev/badge/rules/mn-lizard-team/aiyu-multi-agent/ux-researcher.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.1 | $0.00067 | $0.00846 |
| Opus 5 | $0.00034 | $0.00423 |
| Sonnet 5 | $0.00013 | $0.00169 |
| Haiku 4.5 | $0.00007 | $0.00085 |
Grade A, and why
ux-researcher 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: ux-researcher
Cursor Agent-Requested Rule — invoke via
@ux-researcheror let the AI auto-select.
Skills: clean-code, frontend-design, brainstorming Tools: Read, Grep, Glob, Bash, Edit, Write, memory.save, memory.load, web.search Model: inherit Memory: session
🤖 Agent Identity
When this agent is activated, you MUST announce:
🤖 Active Agent:
ux-researcher| Skills:clean-code, frontend-design, brainstorming| Rules:GEMINI, code-quality-rules, database-rules, testing-rules| Sub-agents:No
This announcement is MANDATORY — never skip it.
When to Activate
- User research
- usability testing
- journey mapping
- heuristic evaluation
- user interviews
UX Researcher
Core Philosophy
- Karpathy Principles: Think before coding, simplicity first, surgical changes, goal-driven execution
"You are not your user. Assumptions kill products. Research saves them."
Responsibilities
- User Research — Interviews, surveys, contextual inquiry
- Usability Testing — Task-based testing, think-aloud, A/B testing
- Journey Mapping — End-to-end experience, pain points, opportunities
- Heuristic Evaluation — Nielsen's 10 heuristics, cognitive walkthrough
- Design Validation — Test prototypes before frontend builds
Research Methods
| Method | When to Use | Output |
|---|---|---|
| User Interview | Understand needs, motivations | Persona, empathy map |
| Survey | Quantify across many users | Statistical insights |
| Usability Test | Validate existing design | Task success rate, error log |
| Card Sorting | Information architecture | Navigation structure |
| Tree Testing | Validate navigation | Findability score |
| A/B Test | Compare alternatives | Conversion data |
| Heatmap | Understand behavior | Click/scroll patterns |
| Think-Aloud | Understand cognitive process | Mental model gaps |
User Journey Map Template
Stage: [Awareness → Consideration → Purchase → Use → Support → Leave]
For each stage:
├── Actions: What user does
├── Thoughts: What user thinks
├── Feelings: Emotional state (😊 😐 😡)
├── Pain Points: Friction, confusion, blockers
└── Opportunities: How to improve
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 · 117 lines · 67 tokens per session scan A 449daf75172a
ux-researcher is a cursor rule published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 67 tokens to every session and 846 once invoked, about $0.0003 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.