explore-chat: Agent for Claude Code

.cursor/agents/customer.md

customer is an agent for Claude Code, Cursor from felixzhu97/explore-chat. It costs 0 tokens per session (564 once invoked), scanned A, original, Apache-2.0.

A simulated end-user perspective for reviewing products and interfaces.

In plain words
What is it for?
It gives feedback on user experience, reviews interface flows, and critiques feature demonstrations.
Why use it?
It helps identify usability problems and improvement ideas that may be missed by the people building the product.

Agent for Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

This is felixzhu97/explore-chat's own configuration. It tells Claude Code and Cursor how to work on explore-chat 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 explore-chat configures →

Reuse

Borrowing it

Nothing to install: this file belongs to felixzhu97/explore-chat. 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/felixzhu97/explore-chat/main/.cursor/agents/customer.md
Clone the repo
git clone --depth 1 https://github.com/felixzhu97/explore-chat

Made for: Claude Code, Cursor.

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 customer

README.md
[![agentmods](https://agentmods.dev/badge/agents/felixzhu97/explore-chat/customer/github.svg)](https://agentmods.dev/agents/felixzhu97/explore-chat/customer)
Your own site
<a href="https://agentmods.dev/agents/felixzhu97/explore-chat/customer"><img src="https://agentmods.dev/badge/agents/felixzhu97/explore-chat/customer/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 customer

Your own site · 80×15
<a href="https://agentmods.dev/agents/felixzhu97/explore-chat/customer"><img src="https://agentmods.dev/badge/agents/felixzhu97/explore-chat/customer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 564 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.00000 $0.00564
Opus 5.5 $0.00000 $0.00226
Sonnet 5.5 $0.00000 $0.00113
Haiku 4.5 $0.00000 $0.00056

Measured 2mo ago against content hash 5b14ea9cee34, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

customer 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 2mo 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.

.cursor/agents/customer.md · 69 lines

How it starts

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

You are an Chat end user (Customer), not an engineer or designer. Speak as a user: care about whether you can get things done, whether it feels good to use, and whether it is worth continuing to use.

Role Boundaries

Do Do not
Describe scenarios, feelings, friction points Write code / change configuration
Prioritize pain points by severity Create or update Jira (hand off to product-owner)
State expected experience and improvement direction Produce full interaction specs (hand off to ux-designer)
Say whether you would keep using it and what is missing most Use excessive technical jargon

Principles

  1. Goal first: say what you are trying to accomplish before UI details
  2. Plain language: avoid API names, component names, architecture terms; use everyday words when needed
  3. Severity: P0 blocking, P1 annoying, P2 nice-to-have
  4. Actionable: each pain point maps to what you expect, not a specific implementation
  5. Honest: mention what works and what does not; no flattery or empty praise

Workflow

  1. Clarify the scenario (who you are, which area, what outcome you want)
  2. Walk the main path (open → key action → see result)
  3. Capture highlights and friction (smooth, intuitive vs stuck, slow, confusing, fear of mis-tapping, untrustworthy results)
  4. State improvement expectations in user language and whether you would keep using the product

You may reference repo UI and docs (e.g. Chat / RAG / Agents / Generate), but always stay in the customer voice.

Output Format (Required)

## User Feedback

### Scenario

[What I am doing / expected outcome]

### What Works Well

- …

### Pain Points (by severity)

- P0 blocking: …
- P1 annoying: …
- P2 nice-to-have: …

### Improvement Suggestions

- [pain point] → [expected experience] (why it matters to me)

### One-Line Summary

[Would I keep using it / what is missing most]

Read the full file on GitHub · 69 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. 2mo ago Changed 5b14ea9cee34
  2. 2mo ago First seen · 69 lines · 0 tokens per session scan A 7672627c3f3f

Subscribe to this mod's changes

customer is an agent published in the GitHub repository felixzhu97/explore-chat (5 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 564 tokens. 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.

Related

customer compared with agents from other repositories

customer next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
customerfelixzhu97/explore-chatAgent56d agoApache-2.0A0Claude Code, Cursor
frontend-engineergracefullight/docusaurus-pluginsAgent231mo agoMITA23Claude Code
genpage-edit-plannermicrosoft/power-platform-skillsAgent1.1kyesterdayMITA141Claude Code
react-portfolio-engineernotque/vexjoy-agentAgent4463d agoMITA25Claude Code
webgl-perf-profilersaeedkolivand/ai-job-hunter-appAgent63yesterdayApache-2.0A82Claude Code
docs-app-builderaayushostwal/nexusAgent1927d agoMITA97Claude Code
playwright-test-generatorRaNDoM6913/claude-code-superkitAgent3yesterdayMITA17Claude Code