agentmods.dev

user-perspective-critic

user-perspective-critic is an agent for coding agents from andrewcigan/vibe-dev-plugin. It costs 81 tokens per session (1,626 once invoked), scanned A, original, MIT.

A product-focused critic that examines a feature from the user's point of view. It reads product rules and test research to ask whether the solution covers real user needs, including spoken Russian input when relevant.

In plain words
What is it for?
Use it during a feature review alongside an engineering or test review. It checks user workflows, product metrics, language-specific input, domain rules, and whether proposed fixes address the underlying problem.
Why use it?
An implementation can pass technical checks while solving the wrong problem or measuring the wrong thing. This review looks for missing user scenarios and challenges assumptions about product goals and data.

Agent

Part of the vibe-dev plugin — 29 skills, 24 agents, 7 hooks shipped together

not rated 5 1mo ago A scan 81 tokens original MIT
View the source file andrewcigan/vibe-dev-plugin
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.

agentmods
npx agentmods add agents/andrewcigan/vibe-dev-plugin/user-perspective-critic
Clone the repo
git clone --depth 1 https://github.com/andrewcigan/vibe-dev-plugin

Or install vibe-dev, the plugin that ships this one along with the rest of its 29 skills, 24 agents, 7 hooks.

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 user-perspective-critic

README.md
[![agentmods](https://agentmods.dev/badge/agents/andrewcigan/vibe-dev-plugin/user-perspective-critic.svg)](https://agentmods.dev/agents/andrewcigan/vibe-dev-plugin/user-perspective-critic)
Your own site
<a href="https://agentmods.dev/agents/andrewcigan/vibe-dev-plugin/user-perspective-critic"><img src="https://agentmods.dev/badge/agents/andrewcigan/vibe-dev-plugin/user-perspective-critic.svg" alt="Measured on agentmods" height="20"></a>
Per session 81 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,626 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00081 $0.01626
Opus 5 $0.00041 $0.00813
Sonnet 5 $0.00016 $0.00325
Haiku 4.5 $0.00008 $0.00163

Measured 5d ago against content hash 362eff2a7046, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

user-perspective-critic 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 5d 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.

agents/user-perspective-critic.md · 150 lines

How it starts

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

User-Perspective Critic Agent

Роль

Top-down критика глазами реального пользователя. Закрывает Dual Critique workflow — engineering perspective + user perspective = merge сильнее каждой.

Запускается параллельно с test-researcher.

Главный принцип

«Я тяну bottom-up из кода. Пользователь думает top-down от своей задачи.»

Конкретные примеры из проекта с документным ассистентом:

  1. Метрика 26.7% retrieval — агент доверился, оптимизировал. Владелец продукта: «давай проверим что реально возвращает retrieval» → метрика была сломана, реально 74%.
  2. Агент хотел исправить eval set (убрать вариант написания). Владелец продукта: «нет, это реальный кейс — люди произносят неправильно, система должна выдержать».
  3. Агент предлагал glossary patches (incremental). Владелец продукта: entity-first retrieval (structural fix).

Не bottom-up «фикс кода». Top-down «фикс продукта для пользователя».

Что получаешь на вход

  • Описание активной фичи
  • docs/PRODUCT.md — обязательно
  • domain-rules.yaml — обязательно (особенно invariants, disambiguation_triggers, target_markets, glossary)
  • Описание тестов от test-researcher (когда он закончил) — для критики покрытия

Внимание: ты НЕ читаешь код. Ты читаешь только бизнес-документы.

Что должен сделать

Шаг 1: Read business docs

  • PRODUCT.md (что и для кого)
  • domain-rules.yaml целиком
  • Если есть docs/business-survey.md или user-stories.md — тоже

Шаг 2: Поставь себя на место пользователя

Конкретно:

  • Это пенсионер? Школьник? Юрист? B2B-собственник?
  • На каком языке говорит? На каком устройстве? В каких условиях?
  • Что он делает ДО того как зайдёт на эту фичу?
  • Что он делает ПОСЛЕ?
  • Какая его реальная цель (не «нажал кнопку» — а «получил результат который ему нужен по работе»)?

Шаг 3: Top-down вопросы (мозговой штурм)

Пройдись по списку:

  1. «Какой пользовательский сценарий не покрыт?»
    • Что делает реальный пользователь, что test-researcher не учёл?
    • Особое внимание: voice input, нестандартные написания, нишевая специфика (если применимо)

Read the full file on GitHub · 150 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. 5d ago First seen · 150 lines · 81 tokens per session scan A 362eff2a7046

Subscribe to this mod's changes

user-perspective-critic is an agent published in the GitHub repository andrewcigan/vibe-dev-plugin (5 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 1,626 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-31.

Design and UXai-agentsclaude-codeclaude-code-pluginharnessvibe-coding
Related

Other agents, from other repositories

security-reviewer

Reviews a Wave's diff for OWASP Top 10 vulnerabilities introduced in this change. Triggered automatically by /mumei:compose after a Wave is implemented. Demands HIGH confidence for non-critical findings — false positives erode trust. Does NOT cover code quality, spec, or correctness.

iroha924/mumei · 63 tokens

spec-compliance-reviewer

Reviews a Wave's implementation against requirements.md and tasks.md to detect AC drift, scope creep, missing acceptance criteria, over-engineering, and silent re-interpretation. Triggered automatically by /mumei:compose after a Wave is implemented and before the review phase completes. Does NOT review code quality…

iroha924/mumei · 78 tokens

agy-worker

CLI-backed mechanical implementer — the agy variant of fast-worker. Use for boilerplate implementation, test scaffolds, rename sweeps, or applying an already-approved plan/fix-spec when the session wants the work offloaded to the agy (Antigravity) CLI backend (default model Gemini 3.6 Flash (High)) as a cheap…

hmj1026/dhpk · 203 tokens

code-reviewer

Expert code review specialist. MANDATORY final step before replying after any source-code Edit/Write, or after modifying .claude/ markdown (rules/agents/skills/commands/hooks/scripts) or any CLAUDE.md file. Reviews quality, security, and maintainability. Do NOT skip when: user approved a plan, change seems small…

hmj1026/dhpk · 103 tokens

codex-worker

CLI-backed mechanical implementer — the codex variant of fast-worker. Use for boilerplate implementation, test scaffolds, rename sweeps, or applying an already-approved plan/fix-spec when the shared selector chooses the Codex CLI backend (default gpt-5.6-luna @ xhigh) instead of the in-process sonnet worker.…

hmj1026/dhpk · 174 tokens

spec-miner

Behavioral-spec extraction specialist. Mines flat Requirement / Invariant blocks (with id / entities / enforced / test metadata) from a brownfield codebase into openspec/specs/ /spec.md. Self-bootstrapping — no codebase-onboarding dependency. Use when onboarding an existing project to spec-driven development ("mine…

hmj1026/dhpk · 105 tokens